Identify and Correct a Large SQL Server Error Log
Learn how to find and remove a large SQL Server Error Log file when it consumes a lot of space on your drive
2022-08-03
Learn how to find and remove a large SQL Server Error Log file when it consumes a lot of space on your drive
2022-08-03
In this tip we look at how to parse the SQL Server error log to only extract the errors and corresponding error messages.
2021-02-01
2017-05-22
1,002 reads
2017-04-03
1,097 reads
The code in this tip will show how to use two system stored procedures to identify all iterations of a given string in the available SQL Server error logs since a specific point in time.
2014-01-23
3,148 reads
2017-02-02 (first published: 2013-09-16)
17,529 reads
How do I find out where the SQL Server Error Log file is located for a specific SQL Server instance? In this tip we look at different ways a DBA can identify the location of the SQL Server Error Log file used by an instance of SQL Server.
2011-10-27
3,019 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