SQL Server, performance, data, analytics
admin I’ve updated SQLDiagCmd, my standalone executable for running any or all of Glenn Berry’s excellent SQL Server DMV diagnostic scripts.
As well as being able to target multiple servers and multiple databases, it now also has the option to exclude specified queries from being executed (such as those that might take some time to execute on large very databases or busy server instances).
The source code is available on GitHub and you can download the executable directly from these links:
I was searching through email today looking for a LINQPad snippet that a colleague, James Miles, wrote some time ago, one which we used to generate the scripts for a production SQL Server database + transaction log point in time restore after IT had a little SAN mishap!
In doing so, I came across this gem from James: Solving Puzzles in C#: Poker Hands, which is not just a great example of writing a recursive function but of problem solving in general. [Where I used to work, we often used to have a Friday puzzle where I tried to come up with or find puzzles that wouldn’t be easy to solve by brute force. This was one of the many times I was thwarted by James and others!]
Starting with the upcoming SQL Server 2017 CU3 and SQL Server 2016 SP2 releases, CXPACKET waits are split into an actionable wait (CXPACKET) and a negligible wait (CXCONSUMER).
(these wait types are already present in Azure SQL Database).
Microsoft have published a useful list of all SQL Server trace flags in a single location:
DBCC TRACEON – Trace Flags
In the past, some of these were poorly documented or hard to find.
I was recently trying to work out why SSAS installed on the same server as SQL Server would not use shared memory for its processing connections. It may be obvious to some people, but an internet search turns up surprising few references: the Shared Memory Protocol is not Supported on SQL Server Failover Clusters.
On a standard SQL Server instance, the Shared Memory protocol can be used when a client is running on the same computer as the SQL Server instance and the Shared Memory Protocol is enabled in SQL Server’s network protocols. (You can check the status of the enabled protocols using SQL Server Configuration Manager).
sys.dm_exec_connections will show you which net transport a client connection is using:
SELECT net_transport FROM sys.dm_exec_connections WHERE session_id = @@SPID;
You can force a client connection to use a specific protocol by prefixing the Server name in the connection string with one of these modifiers:
e.g. Force connection to use the TCP protocol:
Server=tcp:MyServerName;Database=MyDB;Trusted_Connection=True;
In addition, you can force the client connection to use the Shared Memory protocol by using (local) as the server name. You can also use localhost or a period (.) e.g.:
Server=(local);Database=AdventureWorks;Trusted_Connection=True;
New to SQL Server Manager Studio (SSMS) 17.3 is the XE Profiler. This is Profiler-like functionality built-in to SSMS:
SSMS 17.3 has Profiler built-in
Just double-click either of the two entries to create a live trace window (built on the SSMS XE “Watch Live Data” functionality). The event sessions that will be created are named:
A quick and easy SSAS optimisation: turn off flight recorder:
SQL Server Analysis Services Flight Recorder provides a mechanism to record server activity into a short-term log. Information captured by Flight Recorder can be helpful for troubleshooting specific issues, however the load placed on the server when capturing the snapshots and trace events can have a small impact on overall performance. For optimal performance the flight recorder should be disabled unless attempting to capture diagnostic information relevant to troubleshooting a specific problem.
http://byobi.com/2016/01/ever-wondered-whats-captured-in-the-ssas-flight-recorder/
If you are running a SQL Server version prior to SQL Server 2016, and you have a query whose plan just doesn’t seem right and you can’t explain it, try running it with trace flag 4199
SELECT SomeColum
FROM SomeTable
OPTION(QUERYTRACEON 4199)
It enables all the query optimiser hot fixes present in your applied SP and CU version.
Many DBAs enable this trace flag globally (at the instance level).
SQL Server 2016 will automatically enable all prior version query optimiser hot fixes.
SQL Server query optimizer hotfix trace flag 4199 servicing model
SQL Server 2016: The Death of the Trace Flag
Bob Ward’s post has some interesting stuff in it:
It’s not uncommon to see questions on StackOverflow relating to SQL Server connectivity issues. Microsoft support have published the following guide to help troubleshoot connectivity issues:
Solving Connectivity errors to SQL Server
In addition to providing a checklist of items that you can go through, it provides step by step troubleshooting procedures for the following error messages:
There are also troubleshooting guides for Always On and SQL Azure DB connectivity issues:
Troubleshooting Always On Issues
Troubleshooting connectivity issues with Microsoft Azure SQL Database