Making a Difference in Uncertain Times
For some people, it’s not enough to take care of their own households and those of their families and neighbors. They’ve decided it’s important to make a difference in their communities and beyond.
SQL Change Automation enables a new flexible approach to DevOps
In the latest version of SQL Change Automation, we enable you to be more flexible in your approach to Database DevOps and combine elements of both state- and migrations- based approaches. Learn more about the new workflow.
Changing the Path for the Master Database
We as DBAs, changing or migrating databases to a new path is important part of admin’s world. This article helps you with the steps involved to move the Critical 'master' database.
Set Statistics Time Examples for Tuning SQL Server Queries
The SQL Server set statistics time statement displays the number of milliseconds to parse, compile, and execute a T-SQL query statement. This set statement is widely used to assess times to implement a query statement. The set statistics time statement reports the CPU time and elapsed time for performance tuning.
Dynamic SQL Going Haywire
Those who work on various databases, or even those who do not, must have come across the term, Dynamic SQL. Dynamic SQL is basically a programming technique that enables you to build SQL statements dynamically at run time. It allows you to create more general purpose flexible SQL statement because the full text of the […]
How to Attach a SQL Server Database without a Transaction Log and with Open Transactions
You want to attach a SQL Server database that does not have the transaction log files and get the following error: "The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred to the database, or the database was read-only. This error could occur if the transaction log file was manually deleted or lost due to a hardware or environment failure." In this tip I will help you to successfully attach the transaction log to the problematic SQL Server database.
Remote Data Challenges
While working remotely, we still need good security practices and strong data protection.
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