SQLServerCentral Editorial

Other IDEs

This editorial was originally published on Jun 17, 2020. It is being republished as Steve is out of town. Let us know if you've changed your SQL IDEs since then. Most of us use SSMS (SQL Server Management Studio) to manage our SQL Server instances or to write database code. However, Microsoft does give us […]

Stairway icons Database Deployments

Defining the Deployment Contract: Stairway to Reliable Database Deployments Level 2

Level 2 formalizes the behavioral guarantees that a changeset must provide in order to be safely deployed and rolled back. It introduces the deployment contract, checkpoint semantics, and the structural scope of Create and Rollback scripts. Data changes are addressed through a dedicated Update mechanism, with clear boundaries and limitations. By the end of this level, a changeset becomes a predictable and well-defined unit that can be reasoned about independently of execution context.

Blogs

The Book of Redgate: Fun with Images

By

We’ve celebrated our birthday many times at Redgate. In the Book of Redgate –...

Why companies use Palantir and how we help implement it in the Czech Republic

By

Discover how Palantir connects enterprise data, supports AI-driven decision-making and helps companies turn insights...

Why companies use Palantir and how we help implement it in the Czech Republic

By

Palantir is an American software platform that brings together business data from different sources...

Read the latest Blogs

Forums

Pay for Performance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pay for Performance, which is...

Packing and Decoding Device Status Codes with LEFT_SHIFT() and RIGHT_SHIFT() in SQL Server

By john.martin

Comments posted to this topic are about the item Packing and Decoding Device Status...

SQL Server Audit Failures

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server Audit Failures

Visit the forum

Question of the Day

SQL Server Audit Failures

If I have a SQL Server Server Audit setup, what are my options for configuring the instance in the event it can't write to the audit log?

See possible answers