2006-06-05
1,387 reads
2006-06-05
1,387 reads
2006-05-17
1,350 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,276 reads
2006-05-01
1,174 reads
2006-04-27
1,150 reads
2006-04-25
1,380 reads
2006-04-17
1,133 reads
2006-04-14
1,102 reads
SQL Server 2005 builds some great encryption tools into the product, but what if you are stuck with SQL Server 2000? SQL Server expert Michael Coles brings us the first part of a series along with a free toolkit to manage encryption and keys.
2007-06-22 (first published: 2006-04-13)
31,630 reads
The first version of my accounting assistant could not find a single purchase of...
Why isn’t AI paying off yet? Drawing on lessons from digital transformation, Joyful Craftsmen...
By Steve Jones
I’m really excited about some growth in Flyway support. I’ve been asking about this...
Comments posted to this topic are about the item Pay for Performance, which is...
Hi I have this slow query that is pulling data from a linked server....
Comments posted to this topic are about the item Too Many Choices
I have a table, dbo.MasterBrands, with this data:
BrandID OfficialName 1 Samsung 2 Apple 3 Microsoft 4 Adidas 5 Coca-ColaI run this query. What is returned for Coca-Cola?
SELECT CHOOSE(BrandID, 'Conglomerate', 'Tech and Design', 'Desktop', 'Apparel') FROM dbo.MasterBrands;See possible answers