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

Demo for Parameter Sniffing and Memory Grant Feedback

By

Disclaimer: The following is built with Claude Code. Just need to justify my $100/mo...

My Social Media Rules

By

I developed these rules a while back, before COVID. I had a period of...

Why Use TRY_PARSE(): #SQLNewBlogger

By

Someone asked why I would use TRY_PARSE after I posted a question at SQL...

Read the latest Blogs

Forums

Partitioning a table with TEXTIMAGE_ON option

By Brandie Tarvin

I have a table that ends in ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]. I'm about to...

OUTER APPLY Fundamentals: Part 2

By Imran2629

Comments posted to this topic are about the item OUTER APPLY Fundamentals: Part 2

Building Great Software

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Building Great Software

Visit the forum

Question of the Day

The Range of Customers

I have this data in the OrderHeader table in a SQL Server 2025 database (ordered by CustomerID ASC):

orderid orderdate               customerid complete
3       2025-05-10 00:00:00.0002          1
21      2024-01-10 00:00:00.0003          1
15      2023-10-28 00:00:00.0004   1
13      2025-03-08 00:00:00.0006          1
11      2024-04-02 00:00:00.0007          1
If I run this query, how many rows are returned?
SELECT *
 from dbo.OrderHeader
 where customerid between 3 and '6'

See possible answers