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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-10-10 : 09:25:08
|
| Amk3d writes "Sql Server 6.5 service pack 5adatabase size =200MBLog size=100mbI setup a new sql server two months ago for my organization because of a management requirement.since the new server has been setup there have been 2 crashesone was when the sql server was stalled on operning.the microsoft site said that this is because of a master db problembut when I removed our database log device it started up & showed our DB as corrupt.(a very big operation was running & had been stalled just before this incident. this is why I believe our DB log had got currupted)the next incident a couple of days back was again when a progarm had been continously stopped & restarted due to being slow by a client. this time when a back up was taken it gave a error 84096/11/11 18:38:23.37 spid15 Error : 840, Severity: 17, State: 2 96/11/11 18:38:23.37 spid15 Device maindb (with physical name e:\db\maindblog.db, and virtual device number 4 .d) is not available. Please contact System Administrator for assistance.(the physical was the log device)from then onwards we could not update data but could view it until we restarted the server .the problem reoccured when we tried to take a backup.(this time there were 2 log devices )we corrected it by restoring all old backups.(it once gave a CRC error)I believe the log file seems to be getting corrupted when large operations are interupted am I right??????can this be due to faulty hardware. how can I stop this (this did not occur in the old server )I did not get any help from microsoft.comI would very much appreciate any help.thank you." |
|
|
|
|
|
database log device keeps getting corrupted