Security

Technical Article

SQL Server 2000 SP3 and xp_cmdshell Woes

  • Article

The problems caused by the SQL Sapphire Worm, also know as the SQL Slammer, have caused many sites to do a quick upgrade to SQL Server 2000 Service Pack 3 (SP3). It includes the fix that prevents infection by the worm. While moving to the latest service pack is usually a good thing, to do so without thorough testing risks breaking a working application. That is exactly what happened to one of my clients over the weekend.

2005-11-02

2,068 reads

Blogs

Down the Rabbit Hole: Dealing with Ad-Hoc Data Requests

By

"But I don’t want to go among mad people," Alice remarked."Oh, you can’t help...

Adding a Local Model to Ollama through the GUI

By

I saw some good reviews of the small gemma3 model in a few places...

Connect resiliently to SQL Server

By

 Why you should connect resiliently to SQL Server Transient failures happen — in the cloud...

Read the latest Blogs

Forums

using different credentials when debugging ssis

By stan

hi, now and then i want one connection in my ssis pkgs to use...

AlwaysON health check alerts

By Srinivas Merugu

Comments posted to this topic are about the item AlwaysON health check alerts

Bat and SQL script to generate DB user permissions for all Databases in SQL server

By Srinivas Merugu

Comments posted to this topic are about the item Bat and SQL script to...

Visit the forum

Question of the Day

PWDCompare

What does the PWDCOMPARE function do?

See possible answers