Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
steel
Posting Yak Master
107 Posts |
 Posted - 2009-05-08 : 09:37:26
|
| Hi all,I have a production system (Sql 2000+ SP4) on which the MSDB database become suspect due to unknown reason.I don't have backup of the database.PLease help me it is critical...... |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-05-08 : 12:01:42
|
| Can you have a look in the error log. There will be entries in the log detailing why it's suspect. Find them and post them.Why don't you have a backup?--Gail ShawSQL Server MVP |
 |
|
|
fazle_rabbee
Yak Posting Veteran
63 Posts |
Posted - 2009-05-19 : 10:34:37
|
| firstly stop the sql server service manager. Then just go to C/program files/sql server 2000/mssql/data and copy the dbname_data and dbname_log files and paste them to another drive. uninstall the sql server 2000 and then install it again. After that, stop the sql server service manager again and copy those files which have been saved previously to C/program files/sql server 2000/mssql/data and start the sql server service manager. Take backup everyday.fazle rabbee |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-05-20 : 03:09:13
|
| That's major overkill, especially considering that there's a way to rebuild the MSDB database without reinstalling the entire of SQL.Also, rebuilding MSDB may not even be necessary, depending on why to DB is suspect in the first place.--Gail ShawSQL Server MVP |
|
|
|
lightsql
Starting Member
17 Posts |
Posted - 2009-05-27 : 00:33:37
|
| You can perform the following steps to rebuild msdb.1. Stop and start SQL Server using start sqlservr.exe -c -T36082. Detach msdb and rename the damaged msdb file3. Execute instmsdb.sql script4. Restart SQL Server without the trace flag.Hope this works for you! |
|
|
|
|
|
|
Corrupt MSDB database