Increasing deadlocks with NoLock
One of my personal pet issues is with inappropriate use of the NOLOCK hint (and read uncommitted) . Don't get me...
2010-04-23
746 reads
Dave Ballantyne
Cross Apply Ambiguity
Cross apply (and outer apply) are a very welcome addition to the TSQL language. However, today after a few hours...
2010-03-26
1,921 reads
Output = MAXDOP 1
It is widely know that data modifications on table variables do not support parallelism, Peter Larsson has a good example...
2010-03-04
557 reads
Cleaning up sys.dm_exec_cached_plans
Following on from my previous post in which I noticed that SQLServer itself was artificially bloating sys.dm_exec_cached_plans, the next obvious...
2010-01-27
1,123 reads
Microsoft – Follow best practices – Part 2
In addition to my previous post, another best practice is to not use NOLOCK and READ UNCOMMITTED transaction isolation level.
Here’s...
2010-01-25
545 reads
Microsoft – Follow best practices!
Best practice is to use parametrized queries to enable plan reuse. Will someone please tell Microsoft this.
Presently dm_exec_cached_plans on...
2010-01-22
1,011 reads
Age calculation with SQL Server
There seem to be many different methods being suggested to calculate an age in SQLServer. Some are quite complex but...
2009-12-08
1,129 reads
Phil Factor Speed Phreak SQL Challenge Number 3
The latest Phil Factor challenge is now active here . The prize has now been increased to $100...(read more)
2009-12-04
427 reads
My first useful powershell script – capturing performance counters
After playing around with powershell a bit, I managed to do something quite useful. There are a multitude of ways...
2009-11-30
1,764 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