Technical Article

Placing a Mark in SQL Server's Transaction Log for Fall Back

How many times have you had a programmer come to you and say they want you (the DBA) to restore their database to sometime prior to when they accidentally corrupted it? If you are doing FULL transaction logging you can do a point in time recovery to restore the database to just prior to when the corruption occurred. But in order to do that you need to know exactly when the programmer corrupted the data, which in a lot of cases is not known down to the second.

Blogs

Measuring RAG Solutions: Are We Retrieving the Right Information?

By

A RAG pipeline that answers questions in the demo is not the same thing...

Advice I Like: Lots of Ideas

By

“A multitude of bad ideas is necessary for one good idea” – from Excellent...

Building a DBA Agent for Your SQL Server Estate with MCP

By

Yesterday I gave a talk for MSSQLTips called “Building a DBA Agent for Your...

Read the latest Blogs

Forums

Looking for New Blood

By Grant Fritchey

Comments posted to this topic are about the item Looking for New Blood

Server-Level Row Counts for Tables and Views

By Artur Sanin

Comments posted to this topic are about the item Server-Level Row Counts for Tables...

Parameter Sensitive Plan Optimization vs. Parameter Sniffing: What SQL Server Fixes and What It Doesn't

By vgupta

Comments posted to this topic are about the item Parameter Sensitive Plan Optimization vs....

Visit the forum

Question of the Day

Hyperscale Replicas I

What types of secondary replicas are available for the Azure SQL Database Hyperscale edition?

See possible answers