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 |
|
pap
Starting Member
13 Posts |
Posted - 2004-09-28 : 09:59:30
|
| Hello,I am having this errorCould not find the index entry for RID '1693a6250100' in index page (1:4377), index ID 0, database 'msdb'..Any help, I have already update the service pack to 3 but nothing change, I am getting my server to slow and processor frequently in 100%Help please |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-09-28 : 12:20:43
|
| That sounds like database corruption. Run DBCC CHECKDB on all of the databases on that SQL Server. Do any errors show up there?Tara |
 |
|
|
pap
Starting Member
13 Posts |
Posted - 2004-09-29 : 03:50:20
|
| I have run CHECKDB on all databases with NOINDEX and there isn't any error. This kind of error is related with the SQLServer agent, true ?I have some jobs there running all the time every 2 minutes, that's why event log is always full, if I stop SQLServer agent this errors stop.Any idea ?Thanks for your help |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-09-29 : 12:06:34
|
| You should probably reconfigure SQL Server so that it doesn't log so much then. You can add a startup parameter to sqlsrvr.exe for this. Check BOL for details if you are interested in this. It's a switch that you'll have to add.Tara |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-09-30 : 04:21:50
|
| you may want to check the jobs if they're doing what they're supposed to be doing and terminating normally. what is the effect of the error you posted on your server?i search google for your error message and:http://support.microsoft.com/default.aspx?scid=%2Fservicedesks%2Fbin%2Fkbsearch.asp%3FArticle%3D328736 |
 |
|
|
pap
Starting Member
13 Posts |
Posted - 2004-09-30 : 06:03:24
|
| I have disabled all the jobs that I have running on the SQLagent and then I started one by one and at the same time confirmed with the event viewer, I noticed that is only one that is creating this error, so if I delete this job and create it again it will solve the problem, right ? Do I need to create also the DTS related with this job ?I think this problem appeared because the harddisk was full, is it possible ? |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-09-30 : 12:24:53
|
| Of course it's possible. You'll run into a lot of problems if any of the hard disks are full and SQL Server needs to write to it.Tara |
 |
|
|
|
|
|
|
|