Tag Info

Hot answers tagged

5

I have managed to find one solution to this, although it's not as neat as I would have preferred. I've created a second job that checks the last run date on my target job. This is scheduled to run daily, a couple of hours after the target job should have run. If not exists ( SELECT 'x' FROM msdb.dbo.SysJobServers S INNER JOIN ...


4

Polymon from codeplex is ideal for my uses. I'm monitoring not just server availability, but sql agent jobs success, a host of perfmon data, SQL locking/blocking, db and filesystem freespace, and a whole lot more. It has a very nice Powershell interface, so any Powershell script you can imagine, it will run on the schedule you specify and then ...


4

You can use convert (date, GETDATE()) to get just the 'date' part: select GETDATE(), convert (date, GETDATE()) ----------------------- ---------- 2012-11-16 08:58:20.750 2012-11-16 And if you're only ever going to be comparing 'date' parts, it might be worth changing the datatype in your table to DATE, to save having to convert each time you query it. ...


3

I think we might need to dip into sys.dm_os_ring_buffers and sys.dm_os_sys_info to get the CPU utilization data. Please find below the script of Glenn Berry -- Recent CPU Utilization History (SQL 2008/2008 R2 Only) DECLARE @ts_now bigint = (SELECT cpu_ticks/(cpu_ticks/ms_ticks)FROM sys.dm_os_sys_info); SELECT TOP(144) SQLProcessUtilization AS ...


3

If you are looking for free why not try SQL Server Performance Dashboard? The link below is pretty detailed on how to set it up and get it running: http://www.sql-server-performance.com/2007/bm-performance-dashboard-2005/ Like Shawn said though, there aren't that many free ones available but it is pretty easy to roll your own using SQL/CLR and SSRS. If ...


3

I would start with this list of errors, most of the login errors I believe are around 18400+. The only other two I think I would add would be: 18452: Login failed. The login is from an untrusted domain and cannot be used with Windows Authentication.%.*ls If you are prone to disable logins I would include this as well: 18470: Login failed for ...


3

It's a good idea to create SQL alerts in the SQL agent for all errors of severity 16 through to 25. Also create 1 SQL alert for each of these error IDs 823 824 825. I would create an operator that points to an AD group (probably DBA or ITsupport) so that a team can be alerted or you can drop users in and out of that group when you are away so that errors ...


2

I would suggest that they are equally important on physical or VMs. suggest you to create all critical alerts as highlighted by Glenn Berry.


2

To answer your direct question, I'd probably go about that with a dedicated SQL Server Agent Job to toggling the alert enabled status with the duration of that time. To disable that alert: use msdb; go exec dbo.sp_update_alert @name = 'YourAlertName', @enabled = 0; go And then 4 hours later (either as a separately scheduled job, or with just a WAITFOR ...


2

1) If you are using Oracle 11g or later: Starting from 11g Oracle, was been introduced a fixed table, X$DBGALERTEXT, from which you can retrieve all the data what alert.log does. Here is a simple query that retrieves all errors which occured today, like you want. SET linesize 200 pagesize 200 col RECORD_ID FOR 9999999 head ID col MESSAGE_TEXT FOR a120 head ...


2

Well if you are wanting pretty charts and all, there are not to many free ones that I know of that will automagically do all that you ask. In regards to PBM (Policy Based Management), you can run checks against SQL 2000, 2005, and 20008 instances. So I am not sure where it comes up short for you. With your primary requirements, most of that could be done ...


1

I would recommend any error that decodes to a SQL Syntax error. #113 (unterminated comment) and #208 (unknown object name) are particularly ominous.


1

One approach is to use sp_help_log_shipping_alert_job to find the log shipping alert job ID and then use sp_update_job to suspend the job during maintenance. Enable it back when maintenance is done. I don't know whether the job would not immediately send an alert upon being enabled back though.


1

I have had similar issues to this and every time it was caused by a cloned machine where the SQL components had not been renamed (@@SERVERNAME, Database Mail SMTP, and so on). I would check that possibility first. If the LSAlert job is stopped you should not be receiving mails any more.


1

After exploring numerous possibilities, I've found a solution that meets all the requirements and more: Spiceworks Spiceworks is free. Spiceworks is an agentless solution. Nothing has to be loaded on the scanned instance. Spiceworks can send email alerts based on numerous conditions. Spiceworks can monitor logical volume capacity. SpiceWorks is extensible ...


1

If you are using Oracle 11g or later, consider using the ADRCI utility instead.


1

By recompiling/committing the Alert, the double emails have stopped. It must have been a bad commit initially.


1

The solution is not bad, but I would like to introduce you to a more real time one. Instead of just checking the SMS counter every hour, wouldn't you better know when it first happened? I would do the following: add a new column to your table - Alert bit not null default 0 - which will hold info if the customer was alerted about the high number of SMS. ...



Only top voted, non community-wiki answers of a minimum length are eligible