2006-07-05
1,045 reads
2006-07-05
1,045 reads
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,059 reads
2006-06-13
1,210 reads
2006-06-08
1,329 reads
2006-06-05
1,381 reads
2006-05-17
1,346 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,271 reads
2006-05-01
1,167 reads
By Steve Jones
I’m not sure I knew identity column values could not be updated. I ran...
By Steve Jones
We had an interesting discussion about deployments in databases and how you go forward...
By ChrisJenkins
You could be tolerating limited reporting because there isn’t an off the shelf solution...
I have mentioned this several times over several years. Can someone please help me...
SELECT COUNT(DISTINCT Component) AS Found FROM tblComponents WHERE(Component NOT LIKE '%[a-z]%') AND(LTRIM(RTRIM(Component)) = 'GM13622')...
Comments posted to this topic are about the item Remotely Engineer Fabric Lakehouse objects:...
In a SQL Server 2025 table, called Beer, I have this data:
BeerIDBeerName 1Becks 2Fat Tire 3Mac n Jacks 4Alaskan Amber 8KirinI run this code:
SELECT JSON_OBJECTAGG(
BeerID: BeerName )
FROM beer;
What are the results? See possible answers