During a recent development and testing session of SQL Agent Insight, connections to my local SQL test instances were taking over 10 minutes to connect, regardless of the version or edition, and to be honest, it was pissing me off.
After the successful installation of SQL Server 2016 Developer Edition (which is now free), you are more than likely going to want to install SSMS to manage the recently installed instance. You can get the latest build of SSMS here.
Recently I had to do some performance tuning for a client and needed to see which indexes in a specific database were missing to validate a problem query that was taking too long to execute. The following script assisted in that
The built-in procedure sp_spaceused can provide some useful information, especially when an object name is specified; great for showing the finer details of that object.
Here’s an issue that stumped me for a few hours, and finally, the problem has been resolved! The end goal was to display the entire contents of the SQL agent log in a datagridview (dgv) control. While getting the data
Well, here is an odd error message that had me looking in the wrong direction for a few minutes. While attempting to resolve an asynchronous database mirroring issue on a SQL Server 2012 Enterprise instance running on Windows 2008 R2
The following script when run on your SQL Server instance will show all schedules that are disabled but more importantly will show those schedules that have jobs associated with them.
The following is a small T-SQL script that I frequently use to show the jobs on an instance of SQL that are enabled but are not associated with any type of schedule;
I recently came across this minor issue while attempting to get an SSIS package to run via the command prompt. It took me a couple of hours and quite honestly don’t recall how I stumbled upon the solution.