Start Fixing Your DB with Better Code
The best way to improve your database performance is with better code. We all know that, but few of us actually end up making those changes.
The best way to improve your database performance is with better code. We all know that, but few of us actually end up making those changes.
Running Postgres in Docker is great for a quick test but what if you want it to behave like a proper, production-style setup with SSL encryption, certificate-based authentication, persistent volumes, and custom configurations? In this article, we’ll find out how
When you must rollback a deployment of changes, is that a failure of the process? The development effort? Or something else?
In this level of the Stairway to Azure SQL Hyperscale we learn about the read-only layer that speeds up queries.
Searching for a string in database tables has been discussed over the years. There are several approaches to the problem (see References at the end of the article). See how to use SQL to find a string in different types of SQL Server objects and data.
This article shows how you can find which objects in your database might not be valid after schema changes.
When should a DBA get fired? Steve Jones thinks it should be rare and gives you two cases.
SQL Server 2025 introduces a new sys.dm_os_memory_health_history view to make it easier for meatbags like you and robots like Copilot to know if the SQL Server has been under memory pressure recently.
The Koi Security team recently uncovered the first known, malicious MCP server in the wild: a package called postmark-mcp, downloaded over 1,500 times per week, that silently BCCs every outgoing email to an attacker-controlled domain. So, what happened? High-level, a lot: The attacker cloned the legitimate Postmark MCP repository, made one small but nefarious change […]
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