Articles

Technical Article

Migrating VLDB with Log Shipping

You just had a great weekend. You go grab your coffee and before you take a sip a manager grabs you and says, "we need your help." We need to migrate a very large database to our new data center. We need to keep the data in sync and have a short period of downtime when we cutover.

(2)

You rated this post out of 5. Change rating

2010-08-05

3,477 reads

External Article

Database Upgrade to SQL Server 2008 Tools and Approaches

Performing an upgrade is a complex and often risky project. A successful upgrade can provide an organization with a modern platform for development and production. An unsuccessful upgrade can cause lost time and money, and it can create a bad perception for the future.

This paper documents approaches and tools that can help DBAs and developers to achieve successful and mostly painless upgrade of SQL Server databases from Microsoft® SQL Server® 2000 or SQL Server 2005 to SQL Server 2008 (or SQL Server 2008 R2).

2010-08-04

3,731 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 Kertopaten Telpon. 083135766741

By janehui

WhatsApp 083135766741 Jl. Pegirian No.114, RT.007/RW.10, Sidodadi, Kec. Simokerto, Surabaya, Jawa Timur 60145

BCA KCP Kas Palu Barat Telp:Cs.083831618816

By meyhomecapital

Whatsapp:083831618816 Jl. Sungai Malei No.35, Ujuna, Kec. Palu Bar., Kota Palu, Sulawesi Tengah 94111

BCA KCU PALU Telp:Cs.08216977726

By meyhomecapital

Whatsapp:08216977726 Jl. Moh. Hatta No.29, Lolu Utara, Kec. Palu Sel., Kota Palu, Sulawesi Tengah...

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