Why
Just like in the previous blog, the server overview, this one is the server detail. This started as a collection of utilities combined with a common format.
Format
All the stored procedures output to nvarchar(max) and formatted as HTML using tables as needed. The initiating store procedure is the morning report that calls each section as an independent stored procedure. Here is a list of them:
– MorningReport
calling routine and ends the email to the dba email group
– Database status
this is the same used in database server restart check
– Failed login detail
who attempted to log on to a server, and the users failed to provide proper credentials? I also log the source in address. I validate the IP is in the agency range.
– SQL services
checking only the key services
– New sysadmins
Checking for new elevated privileges in the past 48 hours.
– New linked servers
Again, this is only the past few hours of new linked servers.
– Start of procedures
What stored procedures run the SQL server starts up.
– Jobs that are not enabled (paused)
list jobs that are slated to be removed and forced not to run. The main thing here is to make sure a job was not accidentally disabled
– Jobs enabled but not scheduled (no active schedule)
Basically, on-demand jobs had a schedule, but the schedule is disabled.
– Jobs enabled with no scheduled (on demand)
jobs that are not able to run. Or are to be can from an outside scheduler. These are jobs that do not have a schedule defined. Note: example of this is SSRS.
The code is stored in GitHub, as in most of my code if you want to use it. McBratnie/Morning-status-Report: This is an operational report of what happened on your SQL server while you were sleeping. (github.com)
Helping make your databases; fast, reliable, secure, and less downtime. Need help making this happen?
