Improving the response times of queries in SQL Server is a common task for DBAs and developers. In this article, we will talk about how you can effectively use covered indexes to improve your performance, and when you should use them.
2019-12-09
18,236 reads
A common debate in table architecture is whether to use a natural or surrogate key. In this article, I discuss some of the advantages to each method.
2019-10-15
12,861 reads
Security is often something people think about only after they have had a problem. Given that the average cost of a data breach is $3.92 million (SecurityIntelligence 2019) and ransomware attacks have increased 97% over the past 2 years (PhishMe 2019), the "if it's not broke, don't fix it" approach can clearly be catastrophic. Here […]
2019-10-07
9,364 reads
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
By Brian Kelley
If you don't have a plan, you'll accomplish it. That's not a good thing.
By Steve Jones
Today Redgate announced that we are partnering with Bregal Sagemount, a growth-focused private equity...
Comments posted to this topic are about the item Where Your Value Separates You...
Comments posted to this topic are about the item Fixing the Error
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
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