January 7, 2012 at 5:25 pm
Hey all.
I'm interesting in finding info/scripts to look at on "last chance" alerting. We would like to use stored procedures connecting to our db's. We have many production servers that make transactions. I'm not a DBA at all, but I'm looking for guidance. I have built applications and will be working with the dba's.
We use Sitescope currently but its bugging and alerts are set up poorly.
IS using Stored procedures a quick fix until we find a more robust tool? We have 500 clients, each client has its own db on a shared server, about 40 of them. Transactions are in the 1000's per day.
Sitescope logs in using a Database Query
Alerts look like this, with alerts sent up via email
"Applications: Last Chance: proddb19: "Company name"
No Company name Internet payments in the past 2 hours (Off-Peak)
No Company name IVR payments in the past 2 hours (Off-Peak)
No Company name CreditCard payments in the past 2 hours (Off-Peak)"
Our goal is to be more proactive on alerting the db (and the app/server which will be using Orion (Solarwinds))
We use 2003 server still, vmwared.
Any help appreciated.
lyuba
January 7, 2012 at 7:55 pm
http://databases.about.com/od/sqlserver/ht/sqlserveralerts.htm is a option too? or not a good idea
?
January 9, 2012 at 8:21 am
I think you may want to consider looking at some monioting tools. You can set up alerts and use some of the features in SQL Server to do mail and even page you. But it sounds like you may want to have a good overview of not only problems but performance and health of the server in general. Then again I may not be understanding your question.
Some of the tools you may want to look at are RedGate, SQL Sentry, Idera, Confio.
I would start with a list of what do you want to see\be notified of, and then how much can you afford to spend.
Chris
January 9, 2012 at 9:25 am
Thanks Chris. Yes, we use Sitescope and are looking into new tools but currently need a quick fix until funds are avalible for another tool. I'm not a DBA but was recommended to have the dba's write some stored procedures. Is this a "sloppy" way of monitoring, esp for response time's from 500 db's?
January 10, 2012 at 4:47 am
I'm not sure what procedures do for monitoring. they're a way of executing tSQL on the database. So in answer to your specific question, no, don't use procedures.
But in terms of what can you use for monitoring until you pick up a monitoring solution, the two areas I would suggest looking at are the server-side trace and Dynamic Management Objects. With the server-side trace, you use scripts to capture query performance. Here's the books online entry. Dynamic Management Objects (DMO) are system views onto performance data. You can query against them directly. One of the best resources I know of to learn about this is a book by Louis Davidson and Tim Ford. You can purchase a print copy or download an ebook for free[/url].
Those should get you going with what you need. When you're ready for a monitoring solution, I'd like to suggest you check out Red Gate SQL Monitor[/url]. It's a simple monitoring solution, easy to set up and maintain. DISCLOSURE: I work for Red Gate.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply