Contact Us

In order to get information about the amounts of PHYSICAL reads we perform on database files, SQL Server exposes a DMV called sys.dm_io_virtual_file_stats. In addition to information about number of reads and writes, and the amounts of bytes read and written, we also have the io_stall_read_ms, io_stall_write_ms and io_stall, which show information about the amount of time we have to wait when reading from each file. Using the DMV columns, the following script takes a snapshot

Next week, I’m going to visit London and Copenhagen for SQLBits and SQLRally Nordic. It’s going to be intense and fun. SQLRally On Wednesday, March 4, at 4:45PM, I’ll deliver my session “Query Progress Tracking in SQL Server” at SQLRally in Copenhagen. The session talks about a big pain in our job: How can we know when a certain process will finish its execution? It covers the ways SQL Server allows us to track the progress of processes and queries, and exposes some fun inter

New versions have bombastic and catchy features. But a lot of times, the little, hidden features are the ones that matter the most. I already wrote in the past about the small changes that make a difference in SQL Server 2012, and yesterday about the maturity of SQL Server 2014. Here’s another classic example for a feature nobody talked about that can make a huge difference. sys.dm_exec_query_profiles is a new DMV in SQL Server 2014. According to the documentation, this DMV:

One of the most fundamental DMF’s a SQL Server DBA should know is sys.dm_exec_query_plan. This Dynamic Management Function allows us to see the Execution Plan for queries that are either currently running or have been cached. For example, the following query will return the plan for queries that are currently running, along with the statement text, the entire batch the statement belongs to, and some other stuff: [code lang=”sql”] select substring(text, statement_start_offset