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

Technical Article

Hacker's-eye view of SQL Server

  • Article

If a hacker sets sights on your SQL Server, there are four primary methods he can use to take control and carry out unauthorized, malicious activity. I will look at each of these: Password compromise, Account compromise, SQL injection, Buffer overflows

2005-10-07

4,718 reads

Blogs

Audit – Security Compliance Frameworks (Part 1)

By

This blog series on Audit/Compliance/Security, this is first blog where we would discuss about...

Restore SQL Server Database to an OrbStack Container

By

In the previous post, we've built a SQL Server 2025 sandbox in an OrbStack...

Day of Data Baton Rouge Slides and Code

By

Thanks to everyone for attending my talk today at Day of data Baton Rouge...

Read the latest Blogs

Forums

Can You Really Downgrade from Enterprise to Standard and Save Thousands? Here's What Happened

By Pablo Echeverria

Comments posted to this topic are about the item Can You Really Downgrade from...

What is CPU Usage?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item What is CPU Usage?

Limiting Checkpoints

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Limiting Checkpoints

Visit the forum

Question of the Day

Limiting Checkpoints

If I use the -k parameter with a number after it, what does this change in SQL Server?

See possible answers