SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


How fast can I know that the server is going down or is down


How fast can I know that the server is going down or is down

Author
Message
nawillia
nawillia
SSC Veteran
SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)

Group: General Forum Members
Points: 223 Visits: 554
I've been trying to figure out how to get the fastest alert of if a server is going down, is down, or was rebooted.
1. I can tell if a server has been rebooted and can write scripts to check the log file maybe daily.
2. But can I get the server to send out a message that a reboot has been issued?
3. I've also seen where I can set up some kind of alert notification that the system has been up for a short while, possibly indicating that is just coming back online.
4. Lastly what if the server goes down and doesn't come back online, my thought is only a scheduled external monitor would be able to alert to that condition.

Does anyone have any best practices? I'm thinking of setting up 1 and 3 for my small environment.
Any tips/advice would be appreciated.

thanks
MyDoggieJessie
MyDoggieJessie
SSCertifiable
SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)

Group: General Forum Members
Points: 6668 Visits: 7394
Best practices? It depends. Perhaps use a 3rd party software like centreon/nagios, or RedGate SQL Monitor, or Idera free admin tool (all would work).

For options 1 and 3 you could use a start up procedure that sends you an email once the service has been restarted - http://technet.microsoft.com/en-us/library/ms191129(v=sql.100).aspx

______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience" ;-)
nawillia
nawillia
SSC Veteran
SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)

Group: General Forum Members
Points: 223 Visits: 554
thanks. I just needed some good ideas to get my thoughts flowing.
Grant Fritchey
Grant Fritchey
SSC-Dedicated
SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)SSC-Dedicated (39K reputation)

Group: General Forum Members
Points: 39711 Visits: 32639
You could put in a start up procedure that sends you an email each time the server comes online. That wouldn't tell you it was going down, but it would be self-contained. The real issue is that you can't simply have the server tell you it's going offline. Instead, you need another server to watch the first one (who watches the watchmen type deal). You can build this out yourself any number of ways. I liked using SQL Agent to set up a regular job that queries the server. If it fails, you know it's offline. That's one way to do it.

But, as was already said, building your own monitoring suite is a lot of work. Better to buy one. There are so many out there built out so much better than what you'll be able to put together that it just makes sense.

Fair warning, I work for a vendor, but I won't bring up the product.

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
MyDoggieJessie
MyDoggieJessie
SSCertifiable
SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)

Group: General Forum Members
Points: 6668 Visits: 7394
@Grant, yeah I had already thrown the bone in that direction :-)

______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience" ;-)
nawillia
nawillia
SSC Veteran
SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)

Group: General Forum Members
Points: 223 Visits: 554
thanks 2lwe actually use redgate backup pro and love it. the only thing about vendor software is I need to figure what I can do natively to understand truly how it works and my limitations before I can sell it to my bosses.
nawillia
nawillia
SSC Veteran
SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)

Group: General Forum Members
Points: 223 Visits: 554
@mydog... yeah thanks. i hit up the msdn link and was able to put that into place for our servers for a temporary start. i'm going to research some monitoring apps and maybe scripts this week to try and get our environment more tied down. Today i'm going to put in some critical alerts, so any tips on those would be nice.
MyDoggieJessie
MyDoggieJessie
SSCertifiable
SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)SSCertifiable (6.7K reputation)

Group: General Forum Members
Points: 6668 Visits: 7394
To start, I'd recommend setting up default alerts for:
- Error Number 823 - IO/Hardware/System Issue detected
- Error Number 824 - IO/Logical Consistency Check Failed
- Error Number 825 - Read/Retry Warning
- Severity 016 - Miscellaneous User Error
- Severity 017 - Insufficient Resources
- Severity 018 - Nonfatal Internal Error
- Severity 019 - Fatal Error in Resource
- Severity 020 - Fatal Error in Current Process
- Severity 021 - Fatal Error in Database Process
- Severity 022 - Fatal Error: Table Integrity Suspected
- Severity 023 - Fatal Error: Database Integrity Suspected
- Severity 024 - Fatal Hardware Error Raised
- Severity 025 - Fatal Error

______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience" ;-)
Matt Miller (4)
Matt Miller (4)
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12205 Visits: 18574
The SQL service logs when it is being shut down to the Windows event log. Short of it crashing down, you can use WMI instrumentation to have Windows notify you when those notices pop in the log.

System center and third party tools like BlueStripe (I believe that's the name) can also monitor the SQL browser services in your network for a list of "available" servers against the expected list. When a server is shut off, they will disappear from the list and the tool can notify.

----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
nawillia
nawillia
SSC Veteran
SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)SSC Veteran (223 reputation)

Group: General Forum Members
Points: 223 Visits: 554
Thanks again for the helpful information. I was wondering if there is anything in the SQL Log that I should be monitoring with sp_readerrorlog that is outside of those alerts. I looked through our logs, and I didn't see anything outside of 'our' norm.. lots of I/O taking a long time to complete, but no one who can fix that is fixing it (i've sent tons of i/o metrics over the last year and an alert on that would just become daily/hourly noise).

I'm wondering if the sp_readerrorlog would be archaic to do, and I should just find a 3rd party tool that encapsulates all of that. BTW, this is on a DW, so most issues are low priority since we can recreate our DW to the previous day, versus OLTP.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search