2005-11-17
1,347 reads
2005-11-17
1,347 reads
2005-11-11
1,371 reads
2005-11-10
1,453 reads
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
Right out of the box, SQL Server 2005 does not install many of its services (such as SQL Server Reporting Services) or does not have features turned on by default (.NET integration), thereby reducing the attack vectors that hackers could use to compromise your data security.
2005-10-27
2,024 reads
2005-10-25
1,309 reads
2005-10-24
1,204 reads
2005-10-21
1,322 reads
2005-10-18
992 reads
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
By Vinay Thakur
This blog series on Audit/Compliance/Security, this is first blog where we would discuss about...
In the previous post, we've built a SQL Server 2025 sandbox in an OrbStack...
By Steve Jones
Thanks to everyone for attending my talk today at Day of data Baton Rouge...
Comments posted to this topic are about the item Can You Really Downgrade from...
Comments posted to this topic are about the item What is CPU Usage?
Comments posted to this topic are about the item Limiting Checkpoints
If I use the -k parameter with a number after it, what does this change in SQL Server?
See possible answers