Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 447
  • Last Modified:

Restore SQL 2000 database

I have a SQL 2000 server running one database. This database is for historical data only so there are no changes made since the last backup. The database was showing suspect.

I couldn't fix that so I thought I had a brilliant idea.  

I stopped SQL and renamed the MDF an LDF files. I thought I would be able to restore the backup but in 2000, it looks like you have to have an existing database to restore to.

Now I can't re-attach the suspect database, it says the file you've specified is not a valid SQL server database file.

How can I restore a backup to SQL 2000 when the database is no longer attached?
0
ajdratch
Asked:
ajdratch
  • 8
  • 7
1 Solution
 
QlemoC++ DeveloperCommented:
Use a T-SQL command:
   restore database YourDB from disk='C:\Path\To\Backup.bak'
That should work even with a not yet existing DB.
0
 
ajdratchAuthor Commented:
I'm getting closer. I think the original problem was due to the drive the data is on. I get an error message "File 'PLDIST' cannot be restored to 'E:\MSSQL\DATA\PLDATASS.MDF'. Use WITH MOVE to identify a valid location for the file."

I can't figure out how to use WITH MOVE to change the data location to another drive.
0
 
ajdratchAuthor Commented:
This is the syntax I am trying

C:\Program Files\Microsoft SQL Server\90\Tools\Binn>sqlcmd -E -S server2k3  -Q "
restore database pldatass from disk='c:\temp\pldatass.bak' with move 'pldatass'
to 'c:\sqldata\pldatass.mdf' move 'pldatass_log' to 'c:\sqldata\pldatass.ldf'"
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
QlemoC++ DeveloperCommented:
If you didn't change the logical names of the DB files, your syntax is almost correct, just a comma missing:
sqlcmd -E -S server2k3  -Q "
restore database pldatass from disk='c:\temp\pldatass.bak' with move 'pldatass'
to 'c:\sqldata\pldatass.mdf', move 'pldatass_log' to 'c:\sqldata\pldatass.ldf'"

Open in new window

Else you'll first have to seee how the logical file names are chosen. The SQL is
restore filelistonly from disk='c:\temp\pldatass.bak'

Open in new window

Then use those names as logical names (instead of 'pldatass' and 'pldatass_log').
0
 
ajdratchAuthor Commented:
When I run the filelistonly it shows pldist for pldatass.mdf and pldist_log for pldatass_log
Logical file 'pldatass' is not part of database 'pldist'.

This is what I ran
C:\Program Files\Microsoft SQL Server\90\Tools\Binn>sqlcmd -E -S server2k3  -Q "
restore database pldist from disk='c:\temp\pldatass.bak' with move 'pldatass' to
 'c:\sqldata\pldatass.mdf', move 'pldist_log' to 'c:\sqldata\pldatass.ldf'"
0
 
QlemoC++ DeveloperCommented:
You've replaced the DB name, but you need to change the names in single quotes (but not the file names), as you did already correctly for the log file:
sqlcmd -E -S server2k3  -Q "
restore database pldatass from disk='c:\temp\pldatass.bak' with move 'pldist' to
 'c:\sqldata\pldatass.mdf', move 'pldist_log' to 'c:\sqldata\pldatass.ldf'"

Open in new window

0
 
ajdratchAuthor Commented:
Thanks so much, I ran the command so many ways I didn't realize the last one had the name wrong.

Now the database is mounted but it is called PLDIST. How can I change it to pldatass?
0
 
QlemoC++ DeveloperCommented:
If you used
   restore database pldatass  ...
the database is called pldatass.
0
 
ajdratchAuthor Commented:
I thought I did but I rebooted the server so i don't have the command window up any more to look at what I ran.

I ran EXEC sp_renamedb 'pldist', 'pmdatass'

It said it was successful however the name is still showing as pldist
0
 
QlemoC++ DeveloperCommented:
Probably you are still looking at the logical name of the datafile. That one has not changed.
0
 
ajdratchAuthor Commented:
I am looking in enterprise manager. I tried connect from a client and it can't log into the database pldatass. Does it matter what it shows in enterprise manager?
0
 
QlemoC++ DeveloperCommented:
Can you show us a screenshot from Enterprise Manager?

I'm a little puzzled now. You said the backup is from the same db, but you have changed the db name and location, as we can see. Is the backup from a different server? In that case SQL users will not be available yet.
0
 
Anthony PerkinsCommented:
Does it matter what it shows in enterprise manager?
It only matters if you have not refreshed.  Alternatively just use something like this:
SELECT *
FROM sysdatabases
0
 
ajdratchAuthor Commented:
I uploaded the file. Can I copy that database to a new one with the correct name?
Screenshot.JPG
0
 
QlemoC++ DeveloperCommented:
As I have said, the name of the DB in the restore command determines its name - I don't know why it should show with the original name, unless you have done some more operations without refreshing the list in Enterprise Manager ... You can try again with the restore command, making sure a different DB name is chosen.
0
 
ajdratchAuthor Commented:
Thanks for all your help. To get the name correct in Enterprise manager,  I detached the database and when I re-attached it, I was able to specify the name
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

  • 8
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now