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 |
|
psychotic_savage
Starting Member
25 Posts |
 Posted - 2010-10-28 : 06:28:43
|
| I was wandering what Alerts everyone alerts on or performs a task on.Here is my list.All severity levels above severity 12 - These mail a distribution group and also contain a small description and link to a relative website for assistance.All log files if they go above a set size - Mails a distribution list.Combined log file size exceeds a set amount - Runs a task to shrink the largest 2 log files.All data files if they exceed a set size - Mails a distribution list.All alerts also send an sms(text) alert to my mobile and if there are any data file alerts or alerts over severity 18 a call center is also alerted to notify a list of people.So far I've only worked in 4 environments and none had any alerts so I'm still new to what should be monitored :)Are there any other alerts you would use as your default? |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-10-28 : 10:22:34
|
| - Failed jobs- Drive space below 20% free- CPU pegged- SQL Server service stopped- SQL Agent service stopped- Server doesn't respond to ping- Login as sa- DDL attempted on certain production servers (not all)- Replication failure- Cluster failoverI alert (email and ssms) on all of these. There's a couple more I'm sure, but that's off the top of my head.By the way, I won't automatically shrink a log file in any circumstances. I'll investigate why it grew and if it needs to stay at that size. For example, a one-time mass delete warrants shrinking. Normal activity does not. If your logs are growing out of control, need to increase log backup frequency. |
 |
|
|
csaha
Yak Posting Veteran
52 Posts |
Posted - 2010-10-29 : 11:25:19
|
| I am planning to run the following in production as one of the database log file is huge because I had not turned on the transaction log so can I proceed? I was concerned when you said log file must not be shrink in any circumstances.USE [<DBName>]GOCHECKPOINTGOBACKUP LOG [<DBName>] TO disk='<Backup Location>'GODBCC SHRINKFILE(<DBLogfileName>, <size>)GO |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-10-29 : 11:28:49
|
| I didn't say never shrink, I said never use auto-shrinkIf you've been in full recovery model and forgot to do tran log backups, then yeah, do a one time shrink after you backup the log |
|
|
|
csaha
Yak Posting Veteran
52 Posts |
Posted - 2010-10-29 : 11:58:59
|
quote:
Originally posted by russell
I didn't say never shrink, I said never use auto-shrinkIf you've been in full recovery model and forgot to do tran log backups, then yeah, do a one time shrink after you backup the log
My apologies! I am learning and this forum has already answered lot of questions, thank you. |
|
|
|
X002548
Not Just a Number
15586 Posts |
|
|
|
|
|
|
|
What events do you alert on.