Fragmentation

Technical Article

No Significant Fragmentation? Look Closer…

  • Article

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

A New Word: Semaphorism

By

semaphorism – n. a conversational hint that you have something personal to say on...

SQL Server Linux Container Images Got Smaller: Image Size and Startup Time Across Cumulative Updates

By

This week I was at PASS Data Community Summit in Seattle, and I attended...

Using AI to Build Semantic Models, Ontologies, and Fabric Data Agents

By

(This is the third post in a three-part series on how AI is changing...

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...

Layanan BCA KCP Mahendradata Hub/Wa. 0817-819-444

By layanan 24jam BCA

WhatsApp:0817819444 Jl. Mahendradatta Selatan No. 99 AX, Padangsambian, Kec. Denpasar Bar., Kota Denpasar, Bali...

Alamat Telp BCA KCP Sesetan Hub/Wa. 0817-819-444

By Halo_BCA

WhatsApp:0817819444 Jl. Raya Sesetan No.301, Sesetan, Denpasar Selatan, Kota Denpasar, Bali 80223

Visit the forum

Question of the Day

Adding Bits I

I have a table, dbo.bittest, where I am testing an application response. This has this structure:

CREATE TABLE [dbo].[BitTest]
(
[insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()),
[a] [bit] NULL
) ON [PRIMARY]
GO
My application runs this code:
INSERT dbo.BitTest
(
    insertdate,
    a
)
VALUES
(DEFAULT, 'true')
GO

See possible answers