This is a link to previous related posts that you may find interesting https://sqlserverutilities.com/maximize-sql-trace/ https://sqlserverutilities.com/use-sql-trace-to-capture-database-exceptions/ If we want to capture all the commands being sent to the database engine we should capture just these 2 events: SQL:BatchCompleted and RPC:Completed. By doing so we guarantee to be capturing all executions sent to the database engine which […]
In this post I will discuss and present some practical use cases for SQL Trace also known as “Server Side Trace”. Before we move forward I would like to first make the distinction between SQL trace and SQL Server Profiler. SQL Trace is a database engine technology while SQL Server Profiler is a .NET application
For the previous post discussing SQL Trace see this post For the TraceExceptions stored procedure presented in this post see my Traces project at Github. Capturing all the exceptions that occur in the database engine has been proved to be very useful in my experience. Actually, when thinking about it, I realize most DBAs do
SQL Server allows marking any stored procedure as a “startup” procedure which means it will get executed upon a service restart. A “startup” procedure has to reside in the master database and cannot accept input parameters – cool, this is something we can live with. I find this option to be very simple and practical
Working with partitions at different environments has led me to think that a generic unified code to manage partitions can be very useful and practical. Think about it, if you look at a code that manages a partition sliding window implemented by 10 different DBAs you are going to see 10 different variations of the
Among the many tasks that are under the DBA’s responsibilities is keeping the database performing well and in good health. And when mentioning performance the topic of indexes is Inevitable. The task of index maintenance typically includes the process of handling indexes fragmentation accomplished by the REBUILD and REORGANIZE commands and wile this is a
SQL Server exposes missing indexes metadata via the following 3 DMVs (Dynamic Management Views) sys.dm_db_missing_index_details, sys.dm_db_missing_index_groups and sys.dm_db_missing_index_group_stats which combined in a simple query return valuable information of indexes that were detected as missing by the Optimizer and logged in those DMVs. The information in these DMVs is updated by the execution of every query
SQLScripter is a powerful command line utility designed to automate the process of schema generation. SQLScripter simply preserves your schema on the file system at many points in time allowing you to easily access any object that you may need, be it a Stored Procedure, a Job, a Login, Partition Function or any other object
In this post I talk about SQL Server Agent jobs when implementing AlwaysOn Availability Groups. AlwaysOn Availability Groups synchronizes the databases that are part of an Availability Group but any other object that is not part of these databases do not get synchronized (i.e. logins, linked servers, operators etc.) and this includes SQL Server Agent jobs. For
Implement SQL Server Agent Jobs with AlwaysOn Availability Groups Read More »
As far as I recall the trigger to code sp_helpindex2 was that with the introduction of INCLUDE columns to indexes that was added in SQL Server 2005 the old way of viewing indexes using sp_helpindex was useless since Microsoft has not modified their procedure to support the recently added INCLUDE columns. I had therefore found myself, when tuning queries,
