Articles

External Article

Recover SQL Server Resource Database

SQL Server Post Update Failure | Troubleshooting - In this tip we look at the steps to recover missing SQL Server mssqlsystemresource database files that cause SQL Server not to startup. This can occur when an update to SQL Server does not complete successfully therefore making these files absent from the folder where they need to reside.

2019-11-06

External Article

Make SQL Server monitoring part of your deployment process for 2020

As we approach 2020, demand for more frequent deployments continues to rise. With this, management of SQL Server availability needs to evolve.

Now’s the time to consider how SQL Server monitoring could improve your deployment performance. In this whitepaper, learn how SQL Server monitoring can help your development and DBA teams work together to remove bottlenecks and enable faster, more reliable deployments.

2019-11-04

Blogs

Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022

By

Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022 ...

Looking Back at the Redgate 2026 Company Kickoff

By

Last week I spent a few days in Cambridge, UK for the Redgate Company...

PASS Data Community Summit 2025 Recap

By

This is long overdue but life and distractions happened. It’s been a little over...

Read the latest Blogs

Forums

Microsoft no longer being supported?

By Richard.Westhaver

The word is finally out that Microsoft is no longer supporting SSRS. I just...

SQL Agent job running gMSA cannot backup to NAS target

By DataMatt43

I'm running a group MSA for the database engine and SQL Agent in a...

sys.query_store_query question

By as_1234

All, My query is as follows: SET DATEFORMAT dmy SELECT p.query_id, DATEADD(MICROSECOND,-rs.max_duration,rs.first_execution_time) AS starttime,...

Visit the forum

Question of the Day

Encoding Strings

I have this code in SQL Server 2025. What is the result?

DECLARE @message VARCHAR(50) = 'Hello SQL Server 2025!';
DECLARE @encoded VARCHAR(MAX);

SET @encoded = BASE64_ENCODE(@message);
SELECT @encoded AS EncodedResult;

See possible answers