Press "Enter" to skip to content

Category: Administration

Updates to sp_Check Tools

Jeff Iannucci has a slew of updates:

We’ve been busy updating our suite of sp_Check tools, but…we forgot to tell you about that. And by we I mean me, so this post from me is to rectify that issue.

Speaking of issues, we have added a bunch of new issues to check for in sp_CheckSecurity recently. Fabiano Amorim and Andreas Wolter have been doing great work writing about SQL Server security issues, and we have tried to keep up with their findings by including new checks in sp_CheckSecurity. We would HIGHLY recommend updating your copy of that tool if you haven’t done so recently.

Click through for the full set of changes.

Leave a Comment

Fixing “Too Many Connections” in Postgres

Achyut Tripathi makes a connection:

Database connections are essential for any program to manage and access data in the database. When a server already has too many active and open connections – a result of a large number of users creating numerous, simultaneous demands on the system – no new connections can open, and the system indicates that it has reached its maximum connection limit.

This issue can be caused by several factors, including connections that are opened unnecessarily and no longer used by the application, programs that create a large number of connections, incorrectly configured connection pools, and a sudden increase in traffic.

When these issues aren’t managed properly, the system encounters request failures – resulting in no new connections being made.

Read on to see how Postgres handles these and what you can do if you find yourself in that situation.

Leave a Comment

Microsoft Fabric Tenant Settings and the Govern Tab

Heidi Hasting sees something new:

Hiya!

“Ooh, what’s this?”

That was me this week, poking around the OneLake catalog. It keeps getting better and better, and I spotted something that made my admin heart very happy. The Govern tab now has Configurations > Tenant settings, right there in the catalog.

Click through to see what’s there. It’s still not ideal for non-admin users, as Heidi points out, but it is a marginal improvement over what was there before.

Comments closed

Capturing Failed Logins in Microsoft SQL

Aleksey Vitsko keeps a list:

Our requirement is to record unsuccessful login attempts i.e. failed logins for security and compliance reasons. The database estate includes SQL Servers, Azure SQL Databases, and Azure SQL Managed Instances. How can I configure auditing for failed logins for each of these database environments?

Read on for the answer in SQL Server, Azure SQL Database, and Azure SQL Managed Instance.

Comments closed

Version Store Accrual and Open Database Transactions

Erik Darling has a video for us:

Erik Darling here with Darling Data and in today’s video we are going to talk about why the version store won’t clear if any database has open transactions. I realized that I read it a little bit differently than it looks there because I had to say it is what we’re talking about where this asks a question, right, so the words don’t precisely line up. But don’t blame the robots for that. That looks weird in the transcript. Anyway, it sounded weird in my head as I was trying to phrase it because I’m looking at the words and trying to rearrange them. That was tough. I’m not as sharp as I used to be.

It’s okay, Erik; none of us are.

Comments closed

Disabling FileStream and FileTable on a SQL Server Instance

Stephane Haby turns off a feature:

A customer recently asked me to disable FileTable/FileStream on their instance because the databases no longer use it, and to ensure that this is indeed the case.
The aim is to migrate to a new architecture without FileTable/FileStream in a second time.

The tricky bit is that the relevant database is also inside of an Availability Group. Click through for the process.

Comments closed

The Power of Group Managed Service Accounts

John Sterrett gets rid of a password:

Somewhere in your environment, a SQL Server service account password hasn’t changed in years. Several people know it, and it’s probably in a script or a spreadsheet. I wouldn’t be surprised if someone hasn’t even put it in an AI chat.  Group managed service accounts (gMSAs) remove that problem.

This past weekend, during my Advanced Security Protection talk (online version you can watch) at Days of Data in Pittsburgh, someone asked: “What are the best practices for encrypting passwords in connection strings?” That reminded me I’m overdue to blog about Group Managed Service Accounts, so here we are, because the best way to encrypt them is to not need to encrypt them.

This does get a lot trickier if you’re not on Windows, and it does require Active Directory. But for most environments, gMSAs are an outstanding idea.

Comments closed

SQL Server 2017 Has One Year of Support Remaining

Brent Ozar provides a reminder:

Even if you can knock out one of these per month on every 2017 & prior instance that you have, you’re still gonna be banging up against the October 12, 2027 deadline.

It’s not like your servers will magically stop working on that date – but if your company’s insurance or compliance rules say you’re not allowed to run out-of-date software, then it might be your butt on the line for not getting onto a supported version. (And if you’re subject to that, and you’re still running on SQL Server 2016, I’d be curious to hear in the comments how your experience went trying to purchase 2016 Extended Security Updates (ESU) from Microsoft.)

Brent has a list, and if you have any 2017 instances kicking, it’d be a good idea to get started on these.

Comments closed

Worker Thread Exhaustion and sp_invoke_external_rest_endpoint

Louis Tochon runs out of worker threads:

With SQL Server 2025, Microsoft lets the database engine call an AI model by itself. sp_invoke_external_rest_endpoint sends an HTTPS request straight from T-SQL, to Azure OpenAI or to any other REST service, so an embedding or a completion no longer needs application code in between.

But what happens under heavy pressure, when hundreds of sessions make that call at the same moment and the model takes its time to answer? I ran this scenario on SQL Server 2025 and on Azure SQL Database, with the same procedure and the same load script. The two platforms do not react the same way at all.

Click through for three tests, covering SQL Server 2025 with and without Resource Governor, as well as Azure SQL Database.

Comments closed