Often in database design we store different values in rows to take advantage of a normalized design. However many times we need to combine multiple rows of data into one row for a report of some sort. New author Carl P. Anderson brings us some interesting T-SQL code to accomplish this.
This Friday Steve Jones talks about the commitments and contracts that you may have with your customers. Do you know what they are? Is the contract explicitly spelled out? Take this Friday's poll and share your answer with everyone else.
Lookup tables can be a force for good in a relational database. Whereas the 'One True Lookup Table' remains a classic of bad database design, an auxiliary table that holds static data, and is used to lookup values, still has powerful magic. Joe Celko explains....
The 2011 edition of MVP Jacob Sebastian's T-SQL Quiz is underway. You can take part in the quiz each day, submitting your answers for the chance to show off your knowledge and perhaps win some prizes.
Today we have an editorial reprinted from Jan 15, 2006 as Steve is on vacation. This one talks about the patching process at Microsoft, and why it sometimes is slower than we might like.
How the JOIN operator works, the different types of JOINs and relevant information about joining tables.
Probably not the kind of change you're expecting. I've recently been contacted by the Kimball Group, and they've asked me...
You need to provide data validation at the server level for complex strings like phone numbers, email addresses, etc. You may also need to do data cleanup / standardization before moving it from source to target. Although SQL Server provides a fair number of string functions, the code developed with these built-in functions can become complex and hard to maintain or reuse.
What happens when you have bad IT people working in your company? Steve Jones says that they always will be around, but we might not want to enable them to continue in this business when we find them.
This article provides a practical example of minimizing the growth of a distribution database.
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