Skip to main content

Morning Checks - Forewarned is forearmed

It’s always handy to know if there any problems with your servers before you get into work in the morning. This is why I wrote a program that goes round all our SQL instances at 7am and checks they are all up. If it doesn’t get a reply from one it emails or pages me to let me know. So I know what to expect when I get in and can “hit the ground running”.

I have a table with the names of all the servers and instances and my program simply works its way through the list this code actually check the state of the Windows service. The service name for the default instance is straightforward but you will need to work out the correct name for your named instances.

Of course there may be occasion where the service reports as running but actually SQL isn’t responding. An alternative method would be to run a SQL command against each instance and see if there is a SQL response. I use that for DBMS and SSAS  but it doesn’t work  for SSIS and a lot harder for SSRS since it’s a web service.

   2:  using System.ServiceProcess;
   4:  string strServiceName = "";
   5:  switch (ServerType)
   6:  {
   7:  case "SSIS 2005":
   8:      strServiceName = "MsDtsServer";
   9:      break;
  10:  case "SSIS 2008":
  11:      strServiceName = "MsDtsServer100";
  12:      break;
  13:  case "SSRS":
  14:      strServiceName = "ReportServer";
  15:      break;
  16:  case "SQLServer":
  17:      strServiceName = "MSSQLServer";
  18:      break;
  19:  case "SQLAgent":
  20:      strServiceName = "SQLServerAgent";
  21:      break;
  22:  case "SSAS":
  23:      strServiceName = "MSOLAP";
  24:      break;
  26:      }
  28:  try
  29:  {
  30:  ServiceController sc = new ServiceController(strServiceName, ServerName);
  31:  switch (sc.Status)
  32:  {
  33:      case ServiceControllerStatus.Running:
  34:  Console.WriteLine(ServerName + "Running");
  35:  break;
  37:      default:
  38:  Console.WriteLine(ServerName +  " ***** Error: " + "Service is " + sc.Status);
  39:  break;
  40:  }
  41:      }
  42:      catch (Exception ex)
  43:      {
  44:  Console.WriteLine(ServerName + " ***** Server Morning Check Error:" + ex.Message);
  46:      }


Popular posts from this blog

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

SQL Server Express v SQL Server Developer Edition

SQL Server Express v  SQL Server Developer Edition
Over the weekend I received the following in an email from Ali Ahmad who asked me some questions about learning SQL Server. We exchanged a couple of emails so I have boiled this down to the most salient points.

Goal: I want to learn SQL Server inside out… for career progression as DBA/BI/data mining. I'm a data analyst and want to learn inside out about data warehousing.
•I understand relational database concepts...
•I have SQL Server 2014 express installed…
•I need to download the adventure works sample in order to play with it.
•So much knowledge on Microsoft website it's easy to get lost… where do I begin?

SQL Server Express v SQL Server Developer
This is interesting. If you want to learn SQL Server inside out including the Business Intelligence suite of applications I would suggest downloading the developer edition of SQL Server which since 2016 has been made available free of charge. Prior to that there was a f…