SQLServerCentral Article

Case Study: Importing New Data Without Emptying Existing Tables

The challenge for Robert Marda was to devise a way to keep the data available at all times while importing the new data, detect if a full or daily update was received and run appropriate data pumps, put in sufficient fail safes to ensure bad data would not get imported, and to make the process automatic including notification to pagers upon failure. Robert shows you how he did it here.

Blogs

In-Person CISA Training – April 13-16, 2026

By

I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...

EightKB 2026

By

EightKB is back again for 2026! The biggest online SQL Server internals conference is...

The FinOps Lifecycle: From Budgeting to Reporting

By

Working in DevOps long enough teaches you two universal truths: That’s exactly why I...

Read the latest Blogs

Forums

query to track time spent on individual tasks in SSIS

By water490

Hi everyone I am looking at building a query to determine how much time...

SQL Server Transactional Replication from Always On Availability Groups to Azure SQL Database

By Terry Jago

Comments posted to this topic are about the item SQL Server Transactional Replication from...

Hidden Heroes

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Hidden Heroes

Visit the forum

Question of the Day

Identities and Sequences I

When thinking of the Identity property for auto incrementing columns and sequences for the same action, which are explicitly linked to increment a number in a table when a new row is added?

See possible answers