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.

Technical Article

forceSQL - Free SQL Password Auditing Tool

forceSQL v2.0 is a much improved version of our SQL Password command-line tool. It now incorporates Brute Force in addition to Dictionary attacks. It works significantly faster because it now bypassess the SQL/ODBC API and directly goes to the network.
A free download and a much more detailed description is available at http://www.nii.co.in/tools.html

Blogs

Claude AI Convinced Me Not to Build an iPad App

By

I coach volleyball and I do a lot of stat stuff on paper. I...

A New Word: Dolorblindness

By

dolorblindness – n. the frustration that you’ll never be able to understand another person’s...

Claude Code Helps Analyze Test Data Manager Log Files

By

I had a customer ask about analyzing their Test Data Manager (TDM) usage to...

Read the latest Blogs

Forums

Data Warehouse Toolkit meets Star Schema: The Complete Reference

By pietlinden

Is there a good syllabus for reading these two together? (Yes, it's called the...

GPX distance and time analysis in SQL Server

By Cláudio Tereso

Comments posted to this topic are about the item GPX distance and time analysis...

The DBA is Dead; Long Live the DBA

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The DBA is Dead; Long...

Visit the forum

Question of the Day

Changing the AG Listener

In SQL Server 2025, if I want to remove an IP from a listener, what do I do?

See possible answers