Articles

Technical Article

Load 1TB in less than 1 hour

This project was done using SQL Server 2005 Enterprise Edition (with SP1 beta) using the BULK INSERT command with 60 parallel input files, each of approximately 16.67 GB. The best time I got was 50 minutes. Hewlett Packard was kind enough to loan me some time one night on the machine they use to do the TPC-H tests. It is an Itanium2 Superdome with 64 1.6GHZ 9M (Madison) CPUs. For the insert tests the system was equipped with 256GB of RAM. The HP SAN configuration is rated at 14GB per second throughput.

2006-05-30

2,290 reads

SQLServerCentral Article

Achieving Server Redundancy at Remote Offices

Everyone wants a highly available system, but achieving 4 or 5 9s of uptime is hard to do. Especially when you have cost limitations. New author Mark Cook takes a look at how his company analyzed the challenges and which method they chose along with some implementation details.

(1)

You rated this post out of 5. Change rating

2006-05-25

5,301 reads

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 Sudirman No.Tlp.083179431643

By wiseenglishedu

Jl. Jend. Sudirman No.277, Cibadak, Kec. Astanaanyar, Kota Bandung, Jawa Barat 40241

BCA KCP Sentral Cikini Hub.0813•7887•595

By JBUAS

BCA KCP Sentral Cikini Hub.0813•7887•595.Jl. Pegangsaan Timur No.1, Cikini, Kec. Menteng, Kota Jakarta Pusat,...

BCA KCP Pajajaran Hub:Cs.083831618816

By myresultinfo

WhatsApp:083831618816 Jl. Raya Pajajaran No.5 & 6, RT.008/RW.09, Bantarjati, Kec. Bogor Utara, Kota Bogor,...

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