External Article

Testing a Flyway Database Migration

Often, we want to test the new version of a database, produced by a Flyway migration, before committing the new migration file, or to test the same migration run on a number of different databases. This article demonstrates how to do it, by generating and using JSON parameter files to run a series of Flyway actions on any number of databases, on any number of servers.

SQLServerCentral Editorial

Knowing When to Respond

I ran into this quote on the Microsoft Learn site, which I thought was a great way to think about how to administer a system: "Without a baseline, every issue encountered could be considered normal and therefore not require any additional intervention." When I've had users file tickets or complain about things not working well, […]

Blogs

The Book of Redgate: Do the Right Things

By

I do believe that Redgate has been very customer focused since it’s inception. I’ve...

How to Connect to SQL Server When Nothing Else Works – DAC

By

It's 2 AM. Your phone is going off. Users can't connect to the application,...

Get a Range of Sequence Values: #SQLNewBlogger

By

I discovered a procedure recently that I wasn’t aware of: sp_sequence_get_range. This post looks...

Read the latest Blogs

Forums

Jabatan Imigresen Certified Translators: Trusted Support for Official Documents

By nicoldavid_01

When preparing documents for immigration in Malaysia, accuracy and compliance are essential. Working with...

Let's Talk Community Events!

By Pat Wright

Comments posted to this topic are about the item Let's Talk Community Events!

that one limitation in replication

By stan

Hi as shown below a replication target requires a primary key.  if we want...

Visit the forum

Question of the Day

Detecting Deadlocks

By default, how often is the SQL Server Database Engine checking for deadlocks?

See possible answers