Reloading after System Crash

Can you be a little bit more specific when you say "the system is not allowing it" with regards to restoring the backup?

"WallOfFame" wrote:

Sorry,

What I mean to say is that the system is not recogniz> Can you be a little bit more specific when you say "the system is not

What kind of backup did you have, a database backup out of RMS or a backup of the drive? What is the file type of the file you are trying to restore? Is it possible you were previously using a different version of SQL Server? RMS 1.2 & 1.3 install MSDE, which is a free version of SQL Server 2000; RMS 2.0 installs SQL Server 2005 Express Edition. A backup from one version is not necessarily going to work with the other.

Glenn Adams Tiber Creek C> Sorry,

Basically what is going on is that I reloaded the same RMS that I was using before 1.2, and the same SQL Server is there. Now my SQL Server is running just fine, however when I open RMS Admininstrator and try to configure my database, it does not recognize the old .mdf database that I was using. Before we shut down the computer each evening we back up our database with a .bck file. The person who fixed my computer took all of the files from my old hard drive and placed them in a folder in my new hard drive. I tried to create a new database in administrator using the most recent .bck file that was recovered from the old hard drive, but it tries to restore over and over again, but cannot restore it from that file.

Another issue, which I am hoping has to do with this same problem, is that I cannot open POS. When I try I get an error message telling me that something isn't specified in 'Version History' and to change something there...I have no idea what this is...

Was this of any more help?

"Glenn Adams [MVP - Retail Mgmt]" wrote:

Basically what is going on is that I reloaded the same RMS that I was using before 1.2, and the same SQL Server is there. Now my SQL Server is running just fine, however when I open RMS Admininstrator and try to configure my database, it does not recognize the old .mdf database that I was using. Before we shut down the computer each evening we back up our database with a .bck file. The person who fixed my computer took all of the files from my old hard drive and placed them in a folder in my new hard drive. I tried to create a new database in administrator using the most recent .bck file that was recovered from the old hard drive, but it tries to restore over and over again, but cannot restore it from that file.

Another issue, which I am hoping has to do with this same problem, is that I cannot open POS. When I try I get an error message telling me that something isn't specified in 'Version History' and to change something there...I have no idea what this is...

Was this of any more help?

"Keith - SRS" wrote:

Try moving the .mdf and .ldf files out of the ...\data directory (default would be C:\ProgramFiles\Microsoft SQL Server\MSSQL\Data), then try creating the database from your backup. The create process is probably just not able to create the files because they already exist. You can reuse the old .mdf & .ldf by using the "Attach" process instead of creating anew database from your backup, but they should be equivalent anyway. If you want to try attaching to the old files, google "sp_attach" and you should find documentation. I'd continue trying to restore the backup as it's easier...

Glenn Adams Tiber Creek C> Basically what is going on is that I reloaded the same RMS that I was using

that's always possible. do you get an error message when trying to create the DB?

Glenn Adams Tiber Creek C> The only .mdf and .ldf files that are in my directory right now are the

How big is your Database file... compare the last few backups - they should be fairly close in size. If their is a BIG difference in the size your db - you might have gotten it corrupted. We backup daily (keep one copy onsite and another offsite) and do restores on a weekly basis - just to make sure everything is working properly.

Danny "Glenn Adams [MVP - Retail Mgmt]" wrote in message news: snipped-for-privacy@TK2MSFTNGP02.phx.gbl...