Performance Myths : Truncate Can't Be Rolled Back
Derik Hammer sets out to disprove another pervasive performance myth : TRUNCATE is faster than DELETE because it isn't logged and can't be rolled back.
2017-06-01
4,663 reads
Performance
Performance Myths: Table variables are always in-memory
Guest author Derik Hammer dismisses the common myth that table variables perform better than temp tables because they are always in memory.
2017-05-11
5,730 reads
Harmful, Pervasive SQL Server Performance Myths
Aaron Bertrand begins a new series around disproving prevalent myths regarding SQL Server performance.
2017-04-13
4,686 reads
Finding the Worst Performing TSQL Statement
Greg Larsen explains how you can use Dynamic Management Objects and stored procedures to return your worst performing T-SQL statements.
2017-03-06
5,202 reads
Performance Surprises and Assumptions : GROUP BY vs. DISTINCT
Aaron Bertrand acknowledges that DISTINCT and GROUP BY are usually interchangeable, but shows there are cases where one performs better than the other.
2017-02-23
8,502 reads
How Incorrect SQL Server Table Statistic Estimates Can Cause Slow Query Execution
Ben Snaidero explains that if you are updating your SQL Server table statistics nightly, but still seeing occasional poor performance with some of the queries being executed against my database, statistics could be the issue.
2017-02-09
4,089 reads
Disconnecting SQL Server connections after query execution
One way to improve SQL Server performance is to use as few resources as possible. In this post Rahul Mehta demonstrates how you can do this by disconnecting queries post-execution with a simple change in SSMS.
2016-12-21
5,620 reads
5 Advantages of Load Balancing For IT Companies
As an IT company, it is crucial that you maintain uptime and monitor the performance of various processes. By making database load balancing a key element, you can ensure that your processes and websites run smoothly. Tony Branson explains.
2016-11-24
5,719 reads
Sparse Columns in SQL Server : Impact on Time & Space
Erin Stellato (@erinstellato) looks into sparse columns in SQL Server – the changes to space requirements and the impact on the write portion of your workload.
2016-03-15
3,581 reads
Combining R and SQL Server to diagnose performance bottlenecks
Using clustering algorithms to analyse index usage data from SQL Server’s DMVs & simplify complex performance investigations.
2017-05-29 (first published: 2015-12-07)
9,870 reads
Blogs
Flyway Tips: AI Deployment Script Descriptions
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
A New Word: Fawtle
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
Post-quantum key exchange – Insurance policy for your packets
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Forums
Where Your Value Separates You from Others
Comments posted to this topic are about the item Where Your Value Separates You...
Fixing the Error
Comments posted to this topic are about the item Fixing the Error
T-SQL in SQL Server 2025: Encoding Functions
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Question of the Day
Fixing the Error
On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:
SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error? See possible answers