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

Why companies use Palantir and how we help implement it in the Czech Republic

By

Discover how Palantir connects enterprise data, supports AI-driven decision-making and helps companies turn insights...

Why companies use Palantir and how we help implement it in the Czech Republic

By

Palantir is an American software platform that brings together business data from different sources...

Wait… Could This Be the End of Index Maintenance?

By

While attending SQLCon and FabCon Europe in Barcelona, there were a lot of announcements...

Read the latest Blogs

Forums

Pay for Performance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pay for Performance, which is...

Packing and Decoding Device Status Codes with LEFT_SHIFT() and RIGHT_SHIFT() in SQL Server

By john.martin

Comments posted to this topic are about the item Packing and Decoding Device Status...

SQL Server Audit Failures

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server Audit Failures

Visit the forum

Question of the Day

SQL Server Audit Failures

If I have a SQL Server Server Audit setup, what are my options for configuring the instance in the event it can't write to the audit log?

See possible answers