SQL Saturday in Dublin for March 2012!
Exciting news, as this is the closest SQLSaturday has even been to home (Edinburgh – UK), so am very excited.
Exciting news, as this is the closest SQLSaturday has even been to home (Edinburgh – UK), so am very excited.
In this post I will go through the SQL Server Wait Type CXPACKET, what is this wait type a symptom of, and how you could go about diagnosing and optimizing the CXPACKET wait type.
Today I ran into the following SQL Server error while trying to run some Filtered Indexes:
Query processor could not produce a query plan because of the hints defined in this query. Resubmit the query without specifying any hints and without using SET FORCEPLAN.
In this post I go through the possible reasons for this Query Processor error, and how to solve each of those.
A simple example on SQL Server’s RECOMPILE query option.
A quick example that shows how to force SQL Server to use a specified index when generating the Query Plan
There is nothing more annoying than having to go through SQL Server code line by line trying to get the formatting of the each statement correct, in order to be able to reach the code. SQL Server (or any SQL Engine) has a multitude of plugins and online SQL code formatting tools. This short post goes through one online tool to format SQL Server code.
I was having issues today with my SQL Server Activity Monitor, it kept timing out every time I tried to see active transactions, and so I devised this wee script which returns the currently active transactions in the instance, as well as the text of the procedure running.
I’ve ran into this wee SSRS issue today, a quick fix mind you, but I thought its worth mentioning.
The issue is in-relation to the error message: Deserialization failed: The ‘DataType’ attribute is not declared. Line X, position Y.
This is really more of a note than an actual post, but here I give the relevant folders that you need to ensure you have your custom DLLs in when running an SSIS package.
When scaling-out your SQL Server Reporting Service, it is essential to consider how your I/O will behave and how you can better utilize your disk configuration for optimum read and write.
One strategy is to partition the Reporting Service TempDB, which can be split onto multiple disks to better take advantage of the underlying SAN or a RAID configuration, and improve request parallelism, especially important when considering a large multi-user deployment of Reporting Service.