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

Can You See Who Forced a Plan

By

I had an excellent group of people in Gothenburg Sweden when I taught there...

Monday Monitor Tips–Finding CUs for My Instance

By

How can I quickly get a CU patch for a system that’s out of...

Why Data Analysts Love PostgreSQL (and You Will Too!)

By

Data analysis is all about wrangling massive datasets. To do that efficiently, you need...

Read the latest Blogs

Forums

GIT Configuration and Automated Release for Azure Data Factory

By Sucharita Das

Comments posted to this topic are about the item GIT Configuration and Automated Release...

workaround for problems that cant be try caught

By stan

hi a peer of mine recalls an error in an edi app that often...

How to commit transaction log during a large ETL process

By Lord Slaagh

Hello SSC! First, I would like to thank everyone who has responded to my...

Visit the forum

Question of the Day

Trigger Order III

I have created these triggers in SQL Server 2022:

CREATE TRIGGER triggertest_tri_1 ON dbo.triggertest FOR INSERT
AS
PRINT 'one'
GO
CREATE TRIGGER triggertest_tri_2 ON dbo.triggertest FOR INSERT
AS
PRINT 'two'
GO
I want to be sure that the trigger with "1" runs first. I decide to run this:
EXEC sp_settriggerorder@triggername = 'triggertest_tri_1', @order = 'first'
What happens?

See possible answers