External Article

Pros and Cons of Database Sharding for Performance and Maintenance

Large databases usually have a negative impact on maintenance time, scalability and query performance. For maintenance, these large single databases have to be backed up daily while the amount of actual changing data might be small. For performance, tables without correct indexes result in full table or clustered index scans. As the data grows the total query time increase linearly. How can we decrease downtime for the maintenance window for large databases and optimize the performance of daily queries?

Blogs

Restore SQL Server Database to an OrbStack Container

By

In the previous post, we've built a SQL Server 2025 sandbox in an OrbStack...

Day of Data Baton Rouge Slides and Code

By

Thanks to everyone for attending my talk today at Day of data Baton Rouge...

Using Claude Code as a Database SRE Agent with the Everpure Fusion MCP Server

By

Here’s the scenario: one of my SQL Server instances migrated to the DR array....

Read the latest Blogs

Forums

PowerBI Question - Data Sources

By Brandie Tarvin

I don't see a PowerBI forum, so I'm posting here. I have a need...

SQL Server Certificates

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server Certificates

Connect an Azure Function to Azure SQL database Using a Managed Identity

By Kunal Rathi

Comments posted to this topic are about the item Connect an Azure Function to...

Visit the forum

Question of the Day

SQL Server Certificates

Which of these is not true for certificates used for SQL Server connections?

See possible answers