Del's answer is accurate, but I can add a little specific SQL Server knowledge if it helps you feel better about things. What is happening is that restoring a SQL Server's master database is the equivalent of a brain transplant for the database instance. Many fundamental "facts" about the database are defined in the master database, so there is no way to guarantee that the instance is in a consistent state at this point. These "facts" that I am referring to go well beyond the obvious (login definitions, database names, locations of primary data files, and the like). For example, after master has been replaced, all of the following may have changed: login definitions, database names, locations of primary data files, character set, collation order, error messages, compiled access plans, and on and on the list goes. So the simplest way, by far, to get the instance back into a consistent state is to bounce the instance using the "new" master database. Therefore, SQL Server posts a message saying that the restore was successful, but SQL must shut down now. As a sidebar, if you look in the SQL Server error log that was active during the restore, you *will* see that SQL actually notifies you that it is shutting down. But what typically happens is that the client software (in this case, TDP), did not write code to handle this special event, so it is not "expecting" the instance to shut down. Therefore, the client software reports that the connection is broken, and it appears as an "error" in the client software, even though everything is fine from SQL Server's point of view.
Just my 0.02. Hope that helps you understand what's going on a little better. Cheers, Chris ___________________________________________ Chris Leonard, University of Iowa ITS DBA 300 USB / 319-384-0801 This communication is protected by ROT-26 encryption. ------------------------------ Date: Wed, 20 Aug 2003 10:42:32 -0400 From: Del Hoobler <[EMAIL PROTECTED]> Subject: Re: Restoring SQL Database Mehdi, When you restore the master database, after the restore is completed, the SQL server is shutdown and you will get the error message. That is documented in the User's Guide. Please read the Appendix carefully about restoring the master database. (It is under "Advanced Restore Procedures".) You may want to get to a supported level of Dp for SQL, which is 5.1.5. ..or at least look at the 5.1.5 User's Guide online which has more detailed information for Advanced Restore Procedures. If you follow the instructions in the manual, and things still don't seem to be working, please call IBM support. Again... you will get an "error" on the screen after you restore the master database. That is expected. Thanks, Del
