Do We Need a PK?
A primary key is a must for every table. Or is it? Steve Jones examines the question.
A primary key is a must for every table. Or is it? Steve Jones examines the question.
Simplify your SQL tasks by giving your queries and stored procedures the ability to iterate over arrays of table names or values.
SQL Server 2008 introduces four new DATETIME datatypes as well as new DATETIME functions.
In an age where commercial interests seem to trump all, it's nice to see someone delivering content out there for free.
SQL Server guru David Poole takes a look at the different integer data types and the impact of each of those on your database.
An exploration of the process of translating a conceptual model to a logical model, and ultimately, a faithful implementation using T-SQL.
In this sample chapter, William R. Vaughn gives you a kick-start on designing relational databases that can perform better, be easier to maintain, and be more successful thanks to a combination of formal rules and informal suggestions to normalize your database.
This Workbench is about using Regular expressions with SQL Server via TSQL. It doesn't even attempt to teach how regular expressions work or how to pull them together. There are plenty of such resources on the Web. The aim is to demonstrate a few possibilities and try to persuade you to experiment with them if you don't already use Regex with SQL Server.
What do IT workers want for Christmas? Let us know in this Friday's poll.
Most SQL Server programmers know to use the SET NOCOUNT command to prevent the number of rows message from being returned to the client. But how does this affect performance? Does it make sense to qualify the owner on your objects? SQL Server guru David Poole brings us some performance analysis of how your stored procedures perform.
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
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