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 |
|
gunnysack
Starting Member
2 Posts |
 Posted - 2004-09-22 : 13:16:33
|
| I am running SQL Server 6.5 on a Win NT 4 server (service pack 5) and I get a "suspect" database after trying to do a manual syslog dump last night. I need any ideas or help or links to help. I'm desperate!!Here's what happened:Dumps are scheduled fro transaction logs at noon and midnight. Our head accountant ran several recalcs and fill the logs in the afternoon and I tried to manually dump them, which I have done before (dump <dbasename> to diskdump, etc).I ususally have to increase the size of the log "device" to kmake enough room to dump the logs. After increasing the device size by 5 Mb, I then expand the log database and enough room is created to dump. This time a single increase of the device size by 5 Meg didn't let me dump so I went back to the device and increased by another 10 Meg. Now when I went to expand the database I got an error about 32 rows being not enough and then the database went to "Suspect" status and I can't get to it to see anything. I tried a sp_resetstatus but to no avail. I don't know how to check the status of the devices versus the database itself and don't know how to begin troublshooting. I have a backup from a week ago but wanted to exhaust any other remedies first because of data loss from the past week. Any help appreciated. Maybe a reference to a database person we could contract to help. |
|
|
Kristen
Test
22859 Posts |
Posted - 2004-09-22 : 13:36:34
|
| Duplicate of http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=40335 |
 |
|
|
|
|
|
Database Suspect problem