March 3, 2009 at 9:24 am
Hi,
Recently i faced a question "how do we know database damage/crash happened in sql server?" and
Can anybody give answer to this question!
Thanks in Advance
Vijaya Reddy
March 3, 2009 at 9:41 am
Some db 'crashes' will generate dumps in SQL error log directory. All db crashes should be reported in the SQL event log.
A DBCC will pick up some formms of database corruption. Basically , you need to run regular DBCCs and scan your error log to pick these up.
thanks
SQL_EXPAT
March 3, 2009 at 9:41 am
running dbcc checkdb is a good way of finding out if your database has any logical and physical errors.
March 3, 2009 at 9:42 am
when you are not able to access data from the database, in case server is fine
Saying this , this is a open end Question what exactly are they looking for 🙂
March 3, 2009 at 10:08 am
prvreddy2000 (3/3/2009)
Recently i faced a question "how do we know database damage/crash happened in sql server?"
Depends what you mean by 'database crash'
If you mean corruption, use CheckDB
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 3, 2009 at 10:16 am
checkdb, which should be regularly run, and error log checks (again, regularly scanned), will alert you.
What you do depends on what you find. Good suggestions above.
March 4, 2009 at 12:52 am
prvreddy (3/3/2009)
Hi,Recently i faced a question "how do we know database damage/crash happened in sql server?" and
Can anybody give answer to this question!
Thanks in Advance
Vijaya Reddy
Above suggestions are good
check this out from Paul Randall should give you more idea:
http://technet.microsoft.com/en-us/magazine/2008.08.database.aspx
March 4, 2009 at 1:05 am
If you mean "How will we come to know that Database is Crashed?" then answer is
1. Run DBCC CHECKDB('DatabaseName') which checks for integrity of database and it reports error found.
Note:
This check can take some time to run (especially for the object database, due to its size). Therefore, If you planning to run this at regular intervals it can lock or block the database while running. It should be run at non-peak times to minimize performance impact.
2. You will not be able query against the database.
3. You will see Dumps created in LOG folder of SQL Server Installation folder.
4. Event Viewer will record this issue.
5. If Log file of database is corrupted then Database will go into Suspect Mode.
6. SELECT DatabasePropertyEX('DB', 'Status') AS [Database Status] will give the current status.
Thanks!
You can also check this video by Paul on How shrink can cause serious fragmentation problem to DB
http://wtv.watchtechvideos.com/topic194.html
Regards,
Sakthi
My Blog -> http://www.sqlserverdba.co.cc
March 4, 2009 at 1:43 am
prvreddy (3/3/2009)
Hi,Recently i faced a question "how do we know database damage/crash happened in sql server?" and
Can anybody give answer to this question!
Thanks in Advance
Vijaya Reddy
You would not really know, unless you check your error logs as part of your early morning check list and also if it is severely damaged this might go into suspect mode and you can see it on SSMS.
Include DBCC checks as your regular maintenance tasks at off peak hours.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply