Articles

Technical Article

No Significant Fragmentation? Look Closer…

If you are relying on using 'best-practice' percentage-based thresholds when you are creating an index maintenance plan for a SQL Server that checks the fragmentation in your pages, you may miss occasional 'edge' conditions on larger tables that will cause severe degradation in performance. It is worth being aware of patterns of data access in particular tables when judging the best threshold figure to use.

You rated this post out of 5. Change rating

2012-03-14

3,229 reads

Blogs

SQL Server Security: Always Encryption

By

As discussed introduction of Always Encryption blog and initial Encryption at rest as TDE...

SQL Server Security – TDE Encryption

By

Transparent Data Encryption(TDE): TDE was initially introduced in SQL Server 2008 Enterprise Edition; this...

A Las Vegas Break

By

Only a little break for me. I’m actually heading to Las Vegas today for ...

Read the latest Blogs

Forums

The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI

By Terry Jago

Comments posted to this topic are about the item The day-to-day pressures of a...

This Week's AI Trust Problem Became Everyone’s Problem

By dbakevlar

Comments posted to this topic are about the item This Week's AI Trust Problem...

Migrate SSRS Reports to PowerBI Report Server in SQL Server 2025

By Deepam Ghosh

Comments posted to this topic are about the item Migrate SSRS Reports to PowerBI...

Visit the forum

Question of the Day

Identities and Sequences III

When thinking of the Identity property for auto incrementing columns and sequences for the same action, which can be used with the BIGINT data type?

See possible answers