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 |
|
ss1011
Starting Member
8 Posts |
 Posted - 2010-04-01 : 15:23:45
|
| Hi,I have a strange issue related to this error. We're using MSDE 2000 db. After a power failure, our db logs reported this error and the application no longer worked.We copied the dbf/ldf files off onto another machine and was able to attached and query tables w/o any issues or data loss. To confirm the db was good, we moved the files again onto another system and, again, attached using enterprise manager (2000) w/o issues. Ran update stats/check integrity w/o issues.We placed the db back onto the original system and it still threw the suspect errors. We then uninstall the app (which removes the MSDE) and reinstalled it fresh just to make sure we got new default db files in place (master, model, etc.). The new app db worked fine, however, once we restored the problem app db, it marked it suspect again.I can't seem to figure out why we cannot get this db to work on this machine. Any suggestions? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
ss1011
Starting Member
8 Posts |
Posted - 2010-04-01 : 17:22:46
|
| It is the usual "database has been marked suspect". There is a reference to torn pages as well in the ERRORLOG. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
ss1011
Starting Member
8 Posts |
Posted - 2010-04-01 : 17:55:42
|
| I couldn't agree with you more, however, the new database continues to work fine. There was some data loss but they've since manually processed those into the new db. I can't find a logical exlanation for this. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-04-02 : 03:17:25
|
| Did you run DBCC CHECKDB on the original machine on the original Master, MSDB and your application database?" There was some data loss" ... "they've since manually processed those into the new db"Not sure how that is possible unless it was cleaned up using CHECKDB - or perhaps you restored from an earlier, clean, backup and the data loss was data entered after that backup (on the original system)? |
|
|
|
ss1011
Starting Member
8 Posts |
Posted - 2010-04-04 : 16:34:52
|
quote:
Originally posted by Kristen
Did you run DBCC CHECKDB on the original machine on the original Master, MSDB and your application database?" There was some data loss" ... "they've since manually processed those into the new db"Not sure how that is possible unless it was cleaned up using CHECKDB - or perhaps you restored from an earlier, clean, backup and the data loss was data entered after that backup (on the original system)?
We didn't. Reason being is that a new install onto the same station worked fine (with the new app db). We decided to use the new master/model/etc and drop in the app db files into the new instance. I think your suggestion would have revealed some more info though. I will have to remember that for next time. |
|
|
|
|
|
|
|
|
marked suspect errors only from one station