Security was a major focus of SQL Server 2005 during its development, both in terms of making the product secure as well as enhancing the options. Security expert Brian Kelley brings us a look at how the paradigm of logins has changed and what you need to look for in SQL Server 2005.
2008-04-11 (first published: 2006-07-05)
118,220 reads
2006-06-15
1,058 reads
2006-06-13
1,209 reads
2006-06-08
1,328 reads
2006-06-05
1,380 reads
2006-05-17
1,345 reads
If you're performing a penetration test or higher-level security audit of your SQL Server systems, there's one test you must not miss. It seems obvious, but many people overlook it: SQL Server password testing. Given the inherent weaknesses compared with more secure Windows authentication, you should especially test for password flaws if you're using SQL Server authentication in mixed mode. Password testing will help you determine how easily others can break into your database and help you ensure SQL Server users are being responsible with their accounts.
2006-05-16
4,339 reads
2006-05-08
1,270 reads
2006-05-01
1,166 reads
2006-04-27
1,145 reads
By ChrisJenkins
Do you spend so long manipulating your data into something vaguely useful that you...
By Steve Jones
It was neat to stumble on this in the book, a piece by me,...
Forgive me for the title. Mentally I’m 12. When I started my current day...
Comments posted to this topic are about the item Microsoft Security Changes and SQL...
Comments posted to this topic are about the item Expanding into Print
Comments posted to this topic are about the item Downtime Caused by the Postgres...
In SQL Server 2025, what is returned by this code:
SELECT EDIT_DISTANCE('Steve', 'Stan')
Assume preview features are enabled. See possible answers