When requesting SQL Server troubleshooting ,don’t send  messages such as “users are complaining of sudden slow performance “ or “this was OK yesterday, but is suddenly very slow” . Usually it’s insufficient to solve the problem. It’s not impossible, but the process slows down.

Detailed information is better. I analyse the problem quicker, you get a solution quicker . Examples of useful information are :

1)Database  server and OS server version.

2)Application related details. For example, BACKUPS are very slow.

3)SQL DDL , meaning Data Definition Language. Normally , this is a CREATE TABLE script .

Using SQL Server Management Studio create  DDLs

4)DML meaning Definition Markup Language . The SQL statements.

5)Data sample . In a format easy to import , this could be a CSV or an INSERT statement

6)If you don’t think it’s a DDL or DML root cause – then send as much detail as possible, such as recent configuration changes, fix packs, error logs –OS and Database Server.

7)Often the problem is a vague performance issue logged by the end-user. These require  SQL Server database troubleshooting  – where an experienced  DBA can work through the problem and resolve the problem .

If you need assistance in generating detailed information , contact me .