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

Don’t Fear the Technology

By

The concern that a particular technology is going to destroy the world seems to...

Creating a Custom SQL Server Security Checklist Using the DoD STIG

By

The STIG is detailed, which is a good thing, but I found myself wanting...

Creating a Local Model Chatbot on Windows

By

After my session at VSLive last week, I had a few questions from the...

Read the latest Blogs

Forums

RegEx Functions III

By Steve Jones - SSC Editor

Comments posted to this topic are about the item RegEx Functions III

Optimized Locking in SQL Server 2025: Fewer Locks, Less Blocking, and the Cases It Cannot Fix

By vgupta

Comments posted to this topic are about the item Optimized Locking in SQL Server...

Finely Tuned Models

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Finely Tuned Models

Visit the forum

Question of the Day

RegEx Functions III

If I run the REGEXP_LIKE() function, does it match values in a case-sensitive fashion, or a case-insensitive fashion by default.

See possible answers