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

A New Word: Lilo

By

lilo– n. a friendship that can lie dormant for years only to pick right...

Learning Database Design and Power BI Performance

By

I spend my days working on and managing SQL Server instances—working days at least,...

Free SQL Training: Dive into Databases This December!

By

Want to learn SQL and get some real practice this December? Check out the...

Read the latest Blogs

Forums

how to calculate an average only if a minimum number of records exist?

By water490

Hi I am working on a rolling average calculation that is not working quite...

Subscribing to a Great New Year

By Louis Davidson (@drsql)

Comments posted to this topic are about the item Subscribing to a Great New...

dont want pkg to abort if someone is in excel source document

By stan

Hi, is there a way when using excel as a flat file source in...

Visit the forum

Question of the Day

The Funny Dynamic SQL

What happens when I run this code:

EXEC sp_executesql N'PRINT 1; GO';

See possible answers