All Data Readers Are Evil
The DBA's Mantra: All data readers are evil. Steve Jones talks about a proposed corollary that might be appropriate to ensure security.
All Data Readers Are Evil
The DBA's Mantra: All data readers are evil. Steve Jones talks about a proposed corollary that might be appropriate to ensure security.
All Data Readers Are Evil
The DBA's Mantra: All data readers are evil. Steve Jones talks about a proposed corollary that might be appropriate to ensure security.
Connection Strategy for Multiple Database Environments
Greg Larsen looks at one way to design your database connection strategy to simplify changing application connections so you can plug-n-play databases with less administrative overhead when the need arises.
SQL Server 2005 log shipping setup using the wizard
Along with some best practices, SQL Server MVP Hilary Cotter shares a log shipping setup process from start to finish.
Easy or Hard
How should we build tools? Should they be easy to use? Or does it make sense to have some things hard to do so that only experienced used choose them. Steve Jones comments on usability and the implications of your choices.
Easy or Hard
How should we build tools? Should they be easy to use? Or does it make sense to have some things hard to do so that only experienced used choose them. Steve Jones comments on usability and the implications of your choices.
Converting Hexadecimal String Values to Alpha (ASCII) Strings
In an interesting exercise in data conversion, Stephen Lasham brings us a nice article on basic manipulations.
Seeing Double
SQL Server allows some interesting index behavior and there's been some debate over whether it makes sense or not. This Friday Steve Jones asks if you have a reason for this.
International Features in Microsoft SQL Server 2005
This white paper introduces Microsoft SQL Server developers to the international features of Microsoft SQL Server 2005. Topics covered include an explanation of Unicode, added support for supplementary characters in SQL Server 2005, the changes in collation in different versions of SQL Server, changes in data types, performance, updates on data providers, and new international support features in SQL Server 2005 Analysis Services and Integration Services.
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