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 Broken Copilot Query

By

I was testing the new SSMS (v22 Preview 3) with Copilot and ran into...

SQL Server Alerts

By

Don’t Let Trouble Sneak Up on You   Most SQL Servers run quietly. Until...

Prompt AI helping with Auditing

By

I had a conversation with a customer asking this question: how can I tell...

Read the latest Blogs

Forums

Create an HTML Report on the Status of SQL Server Agent Jobs

By Nisarg Upadhyay

Comments posted to this topic are about the item Create an HTML Report on...

Building a RESTful API with FastAPI and PostgreSQL

By sabyda

Comments posted to this topic are about the item Building a RESTful API with...

Collation errors...what is best way to deal with it?

By water490

Hi I have a SP that occasionally get this error: Cannot resolve the collation...

Visit the forum

Question of the Day

A Common Split

What happens when I run this code:

DECLARE @s VARCHAR(1000) = 'apple, pear, peach'
SELECT *
FROM STRING_SPLIT(@s, ', ')

See possible answers