Everyday SQL

Blog Post

Trace Flag 3625 Follow Up

Several months ago, I discussed my customer’s intention to enable trace flag 3625. Since that time, we have observed an intriguing phenomenon when encountering a login failure. To demonstrate...

2024-12-13 (first published: )

464 reads

Blog Post

How to Convert FileTime to DateTime

One of my customers recently wanted to rename each of the SQL audit files will the datetime stamp of when it was created. I explained to them the filename...

2025-01-15 (first published: )

508 reads

Blog Post

How to Test Trace Flag 3625

Recently, one of my customers considered enabling Trace Flag 3625 on one of their SQL Servers, but they wanted a way to quickly test its functionality beforehand. For those...

2023-12-22 (first published: )

503 reads

Blogs

Privacy Policy

By

We value your privacy. This policy explains what personal data we collect and why. What...

Why use XACT_ABORT?

By

This came up one day at my work when a developer was using it....

Using AI for Data Conversion

By

I’m sure I’ve never mentioned that I’m an amateur radio operator. Like Vegans and...

Read the latest Blogs

Forums

sp_lock memory leak

By TheRedneckDBA

I spotted this in the release notes for CU17 in SQL Server 2022: KB3616559...

Migration related issue

By LearningDBA

I migrated DB server from 2017 enterprise to 2019 enterprise. After the migration, every...

How Much AI Code Would You Use?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item How Much AI Code Would...

Visit the forum

Question of the Day

Browsing for Instances

I have a SQL Server instance that is not listening for connections on port 1433. By default, all ports are locked down on my server, except for the SQL Server port. What can I do to allow users to connect to the instance without knowing the port?

See possible answers