New DB with same name as old DB

[jenlion]

I have a customer that has created a database on their SQL server. We know that that database will be replaced next month. To simplify reporting, they named the database with the same name that they want the "new" database to use.

(The reason for replacing the db -- we are piloting ERP software. This is the "play" database, later to be replaced with the "real" database).

Project manager told them that they can't drop that database and create a new one with the same name because of issues with log files, or something like that. Does that sound right?

I know we might be able to save the "live" database and restore it over the pilot database. But is there any reason not to simply drop the "pilot" database and then restore the live one onto the server as a new database using the same name?

Hope this makes some sense, please let me know if there are any real-world issues with this.

Thanks!

 

[Catadmin]

When a database is dropped using the DROP DATABASE command it kills all files, data and log. If you right-click & delete it in SQL 2000, it kills (deletes) all files, data and log. In SQL 2005, the right-click -> Delete gives you a pop-up window with the option of keeping the files or deleting the files.

The short answer is, whoever told the customer they couldn't simply delete the db and start over either works with a different database software program or doesn't have a clue.

Hope this helps you out.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"