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

SQL Server Source Control on a $0 Budget

By

The Source Control Dilemma Every DBA has been there. Trying to keep track of...

CHOOSE’ing a Beer: #SQLNewBlogger

By

We recently published an article on CHOOSE at SQL Server Central. I thought it...

Don’t Treat Your Data Catalog Like a Data Museum

By

Introduction Treating your data catalog like a “data museum”—a static collection where information quietly...

Read the latest Blogs

Forums

The Inefficiencies of Kubernetes

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Inefficiencies of Kubernetes

The Backup Space Needed

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Backup Space Needed

Implementing Fuzzy Search in SQL Server Using New Inbuilt Functions

By utsav

Comments posted to this topic are about the item Implementing Fuzzy Search in SQL...

Visit the forum

Question of the Day

The Backup Space Needed

How do I calculate the amount of space needed for I/O buffers during a backup operation?

See possible answers