Secondary is to elaborate or point to resources that has more information about that particular topic.This article do not focus on going from a lower to a higher version of SQL Server, might be additional considerations when upgrading to a higher version.However, the database is not all that you want to worry about.There are things outside the database, which you also should consider.You should run DBCC CHECKDB to validate physical consistency. When you are ready to make the database available for use, you will need to reset database options and delete any extra log files. Next we get a nice long warning that the transaction log has been rebuilt and the consequences of doing that (basically that you need to start a new log backup chain by taking a full or differential backup).If there had been any corruptions we’d have seen the usual output from 2013-01-20 .550 spid51 Starting up database 'Emergency Demo'.Database options will have to be reset,and extra log files may need to be deleted.After the log is successfully rebuilt, the database is placed in DBO Use Only mode.
Warning: The log for database 'Emergency Demo' has been rebuilt. The RESTORE chain was broken, and the server no longer has context on the previous log files, so you will need to know what they were.
If you donot specify the full path, the new log is created in the Windows NTsystem root directory (by default, this is the Winnt\System32directory).12.
Rebuild the log with this code: DBCC TRACEON (3604) DBCC REBUILD_LOG('' has been rebuilt. DBCC CHECKDB should be run tovalidate physical consistency.
i have a msde (mssql) 2000 / v8.0 database that has one corrupted table.
Microsoft SQL Server Management Studio Express can see the database STRUCTURE, but not the data.