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

PostgreSQL: Diagnosing and Fixing a Sequential Scan with No Filter Predicate

By

A sequential scan is not always a problem — PostgreSQL's planner often chooses one...

Giving AI Agents Visibility Into SQL Server with MCP

By

I’ve been thinking a lot lately about what it actually takes to make an...

The Book of Redgate: Profits

By

Redgate is a for-profit company. We look to make money by building and selling...

Read the latest Blogs

Forums

Stop Prompting Your AI Agent. Give It a Playbook.

By Kumar Abhishek

Comments posted to this topic are about the item Stop Prompting Your AI Agent....

Finish the quote

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Finish the quote

Everything I Needed to Know Used to be Found in One Book

By Kathi Kellenberger

Comments posted to this topic are about the item Everything I Needed to Know...

Visit the forum

Question of the Day

Finish the quote

Finish this quote (for a fun Memorial Day question):

Do not try and bend the spoon. That's impossible. ...

See possible answers