External Article

Best Practice for renaming a SQL Server Database

One of the Junior SQL Server Database Administrator in my company approached me yesterday with a dilemma. He was assigned a task to rename few of the databases in Beta and Production environments; the reason being the database name was based on some other project that is no longer relevant to the data which is presently stored within the database. At first I started to tell him, but figured it would be smarter to document the same and share the information.

Blogs

Rolling Back a Broken Release

By

We had an interesting discussion about deployments in databases and how you go forward...

A bespoke reporting solution doesn’t have to cost the earth

By

You could be tolerating limited reporting because there isn’t an off the shelf solution...

Presenting with Visual Studio Code

By

A while back I wrote a quick post on setting up key mappings in...

Read the latest Blogs

Forums

Cross-DB Ownership Chaining problem

By Johan Bijnens

We want to setup a gateway db to host stored procedures which use tables...

Lots of FKs

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Lots of FKs

Real-time On-prem SQL Server Data in Excel – Over the Internet

By Cláudio Tereso

Comments posted to this topic are about the item Real-time On-prem SQL Server Data...

Visit the forum

Question of the Day

Lots of FKs

In SQL Server 2025, what are the most outgoing and incoming FK references a table can have?

See possible answers