12 Ways To Rewrite SQL Queries for Better Performance
Bert Wagner summarizes 12 techniques he's learned over time, from trial and error, for rewriting queries to improve performance.
2019-05-31
Bert Wagner summarizes 12 techniques he's learned over time, from trial and error, for rewriting queries to improve performance.
2019-05-31
Erin Stellato explains the limits on both plan cache size, and number of entries. If you’re seeing plan cache bloat due to an ad hoc workload, take note of the space consumed by your plan cache and consider enabling the optimize for ad hoc setting.
2019-05-31
Scalar functions in Query Plans just don't always show the whole story!
2018-06-04
910 reads
The Query Store captures a history of queries, execution plans, and runtime statistics, which persist within SQL Server and can be reviewed later.
2018-04-12
4,214 reads
You are tasked with examining poor performance for queries on a certain table, or range of tables. Perhaps a sales report is timing out or running unacceptably slow; perhaps your web application is failing to return the result set before the application timeout is reached. You need to find out what's causing the bottleneck, and optimize either the queries used, the table schemata, or both.
2013-09-06
6,400 reads
By gbargsley
In SQL Server environments where transactional replication runs alongside Always On Availability Groups (AGs),...
Disable the sa login in SQL Server (and sleep better)If you run SQL Server...
By Chris Yates
Change is inevitable. What separates thriving organizations from those that falter is not the...
Comments posted to this topic are about the item Create an HTML Report on...
Comments posted to this topic are about the item Be Wary of Data
Comments posted to this topic are about the item Locking Hierarchies
You have a table [dbo].[orders] without a Clustered Index (Heap). The table does not have any other nonclustered indexes! You rund the following command in Read Committed Isolation Level:
SELECTo_orderdate, o_orderkey, o_custkey, o_storekey FROMdbo.orders WHEREo_orderkey = 3877;