2025-05-12
273 reads
2025-05-12
273 reads
2025-04-28
402 reads
This article shows how we were able to migrate a TB size database to new storage with minimal downtime.
2024-01-01 (first published: 2021-02-24)
7,849 reads
2020-12-10
417 reads
2018-06-28
868 reads
Get Logshipping report only when secondary is more than certain time behind Primary.
2017-11-14 (first published: 2017-10-27)
474 reads
2016-05-11
4,469 reads
How to move a log shipping database to a new monitor server without removing and rebuilding the log shipping setup.
2016-04-04
2,509 reads
When you’re reading from a log shipped secondary, you want the duration of restores to be as short as possible. The sproc provided switches the restores to “NORECOVERY” mode, and then switch back to “STANDBY” at the end of the process.
2015-12-11 (first published: 2015-11-23)
3,068 reads
A look at a SQL script solution that can help you easily fail over and back from log shipping scenarios.
2018-12-14 (first published: 2015-09-08)
3,707 reads
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