January 12, 2010 at 9:16 am
Hi, Recently we had a brief outage on our Prod SQL server, SQL runs on a virtual machine and we take snapshots everyday and ship the same to our DR site. when one of our statement feed job (Qtrly) was running this snap was being taken at the same time, as this is a scheduled event. We got alerted when the hourly TLOG backup didn’t happen as this disks were unaccessible, and the log had error messages saying that ‘TEMPDB’ log file was not accessible.
In fact all the files were intact, it’s just for the brief period of time they lost access to these files during the snap operation which usually takes few seconds.
None of our monitors that monitor SQL windows services didn’t complain as all the databases themselves were fine, it’s was only problem with tempdb, atleast that’s what the error log said.
We restarted the box and SQL recovered correctly and everything was fine after that, I just want to be able to monitor the state of each database within the SQL instance externally, using SQL scripts that periodically check the health of each database and other vital stats pertaining to each database.
SQLH2 only works with SQL 2005 and we need some comprehensive set of SQL’s that can be run from our monitoring tool periodically.
“Basically a health check monitor for all the databases”
Thanks in advance.
January 12, 2010 at 9:10 pm
what actually you are trying to do ?
SQL Monitoring depends on manythings to do. Its not a bit or a line to do so.
Its like a research on SQL Server and the processes. Try to be more perfect on what exactly you are looking into.
Cheers,
- Win.
" Have a great day "
January 13, 2010 at 1:50 pm
How are you taking snapshots? Are you using a tool that understands SQL Server and is capable of freezing the databases before you take your snapshot?
If not, then you are running a huge risk of corrupting your databases. If you are, then you need to consider moving your system databases and tempdb to a different volume. This way, you can snapshot the user databases and present them to another instance without affecting tempdb at all (which is recreated during startup anyways and should not be copied).
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply