Blog Post

Log Shipping – Standby Mode

Hello, dear blog reader. This week’s blog is coming to you from the home office. Finally, my son is back in school, and the house has some peace. For...

2022-09-05 (first published: )

278 reads

Blog Post

[How-To] SSRS migration

Good evening. Today’s episode is coming to you from my home office, where I feel motivated to write a blog in the comfort of my home. Today we will...

2022-08-08 (first published: )

1,020 reads

Blog Post

Where are my SQL Server Errors?

Have you ever opened the SQL Server Error Log and wondered, “where are all the errors?” Digging through the Error Log to find what you need can be a...

2021-06-02 (first published: )

897 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