Category: Tools

Jeff Iannucci announces some updates:

It’s been a while since we have updated some of these tools, so we have reviewed a lot of outstanding issues. We’ve also been working on pending enhancements, and now have updates for each of the tools. Moreover, there are more updates on the way soon, as we are planning for a more frequent cadence of updates.

Also, I’ll let you in on a little secret: there are more sp_Check tools on the way. We have a few additional stored procedures we have been testing internally that should be ready for public release in the coming months. We’re really excited not just for the new tools, but also for the future feature updates to the current tools.

Click through for a list of tool updates and the GitHub repo where you can find them all.

Andrew Pruski splits things out:

A while back I wrote a quick post on setting up key mappings in Visual Studio Code…they make presenting (and generally working) in Visual Studio Code really smooth.

But one thing that kinda bugs me is the location of the terminal…I’ve always had it at the bottom, which is generally fine, and I know you can move it around (top, right, left)…however I’ve found that when presenting, space is at a premium. I bump up the font size and this can result in a lot of scrolling through results in the terminal, which ain’t great.

Read on to see how you can make the integrated terminal a separate tab.

Vibhor Kumar describes a PostgreSQL extension:

That’s the promise of pg_background: execute SQL asynchronously in background worker processes inside PostgreSQL, so your client session can move on—while the work runs in its own transaction. 

It’s a deceptively simple superpower:

• Kick off a long-running query (or maintenance) without holding the client connection open
• Run “autonomous transaction”-style side effects (commit/rollback independent of the caller)
• Monitor, wait, detach, or cancel explicitly
• Keep the operational model “Postgres-native” instead of adding another job system  

Read on to learn more about it, including tips on how to use it and some examples of when you might want to use it.

Erik Darling announces a new open-source product:

That is, if you survive the installation process. Active Directory. Domain accounts. Firewalls. Security policies. Additional database servers. Annoying.

Or just send everything to the cloud, somewhere.

I got real tired of dealing with that, so I built a free, open-source SQL Server performance monitoring tool that isn’t any of those things, and doesn’t suck.

This does sound pretty neat, and the Lite version in particular is very intriguing in places where you can’t (or don’t want to) touch the servers.