2006-07-24
1,300 reads
Security
2006-07-21
1,091 reads
2006-07-05
1,043 reads
SQL Server 2005 Logins
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,166 reads
2006-06-15
1,056 reads
2006-06-13
1,203 reads
2006-06-08
1,327 reads
2006-06-05
1,378 reads
2006-05-17
1,342 reads
Password cracking tools for SQL Server
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
Blogs
How to Run Databases on Kubernetes: An 8-Step Guide
In this step-by-step tutorial, learn how to run MySQL, PostgreSQL, MongoDB, and other stateful...
Episode 11 of Simple Talks: Oracle
By Steve Jones
The 11th episode is now live, recorded a few weeks ago at the PASS...
A New Word: Mornden
By Steve Jones
mornden – n. the self-container pajama universe shared by two people on a long...
Forums
What is the best index strategy for a table that gets truncated?
Hi everyone My SSIS package does a bulk insert of csv files into a...
Blob Storage automated downloads
Dipping my toes into the waters of Azure and of course before I get...
Question of the Day
Running Steve's Code
Can you run this code in any of your SQL Server 2019 databases without error?
CREATE OR ALTER PROCEDURE [dbo].[StevesAmazingProc]
AS
SELECT Consumer_ID ,
Trend_Category ,
Bit_Trace
FROM NewWorldDB.dbo.MarketTrend;
GO See possible answers