Skip to main content

Using connection colors in SQL Server Management Studio to prevent database disasters

Every developer has felt that moment of panic: "Did I just run that DELETE statement on production?" A colleague (thanks Jef!) pointed out a nice trick in SQL Server Management Studio to avoid such kind of heart-stopping moments.

Turns out there is simple yet powerful feature in SQL Server Management Studio (SSMS) called Connection colors that does exactly what the name suggests. Let’s find out how to use this feature…

The problem: Context switching gone wrong

When you're managing multiple SQL Server environments—development, staging, and production—it's surprisingly easy to lose track of which connection you're working with. All it takes is one misplaced query execution, and suddenly you're:

  • Dropping tables in production
  • Running test data scripts on live systems
  • Executing resource-intensive queries during peak hours
  • Modifying critical data without proper backups

The consequences can range from embarrassing to career-threatening.

The Solution: Visual connection identification

SSMS's connection color feature provides an immediate visual indicator of which environment you're connected to. By color-coding your connections, you create an instant, intuitive warning system that works at a glance.

To setup a connections color for a new connection in SQL Server Management Studio 21:

  • Open SSMS and click Connect > Database Engine
  • Select a color from the dropdown in the Custom Properties section:

  • Or click on the Custom… button to select a custom color:

 

  • Complete your connection

To setup a connections color for a new connection in older SQL Server Management Studio versions:

  • Open SSMS and click Connect > Database Engine
  • Go to the Connection Properties tab

 

  • Check the Custom Color checkbox and choose a color through the Select… button

 

  • Complete your connection

When you apply a connection color, SSMS colors:

  • The status bar at the bottom of query windows
  • The vertical line along the left side of query windows
  • The border of the Object Explorer (in some SSMS versions)

This visual feedback ensures you can't miss which environment you're in, regardless of where your focus is on the screen.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more