External Article

Demystifying Oracle's Clustering Factor

One of the more confusing statistics in Oracle is one called the clustering factor. Associated with an index, it's actually dependent on the table data, more specifically the distance between 'jumps' for a given index key. Commonly, a 'jump' is the number of blocks between rows containing the given index key starting with the first block found containing that key. If that sounds confusing don't despair, David Fitzjarrell explains in detail.

External Article

The Importance of Maintenance on MSDB

MSDB is a system database used by SQL Server. MSDB stores all sorts of data, such as backup history, log shipping monitor history, SSIS packages and Service Broker queue data to name a few. Just like user databases, MSDB needs regular maintenance, including index optimizations and, more importantly, regular purging. In this article, Tim Radney looks at how neglecting your MSDB can negatively impact on your environment.

Blogs

Overcoming Imposter Syndrome: A Plan

By

My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...

Advice I Like: Celebrate Success

By

“On the way to a grand goal, celebrate the smallest victories as if each...

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

Read the latest Blogs

Forums

BCA KCP Dewi Sartika Tlpn/wa:085373737551

By SoftwareLicense4u

Jl. Dewi Sartika No.15, Sayang, Kec. Cianjur, Kabupaten Cianjur, Jawa Barat 43213

BCA Finance Bekasi Layanan Mobil Telpon/WA:085188120691

By Matylda Mcdonald

BCA Finance Bekasi Layanan Mobil Telpon/WA:085188120691 KOMPLEK MEGA OFFICE PARK, Jl. Harapan Indah Boulevard...

BCA KCP Ketapang Telpon/WA:08137887595

By techwebsite013

BCA KCP Ketapang Telpon/WA:08137887595.Blok A/3-4, Ketapang Indah, Jl. KH Zainal Arifin, Krukut, Kec. Taman...

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers