Our resident SQL Server security expert, Brian Kelley, went with the SQLServerCentral.com crew to the 2004 PASS Summit in Orlando last month. He was kind enough to jot down a few notes on the conference for those of you that weren't there and are considering going next year.
2004-10-12
4,145 reads
Every shop with any sort of IT organization should be scanning for vulnerabilities and issues with their systems and SQL Server is no exception. Security software vendor has a tool that can scan and report on all your SQL Servers is an easy to use product called Typhon III. Our security expert Brian Kelley takes a look at this product.
2004-10-07
13,905 reads
Do you run an anti-virus product on your SQL Servers? After all, it's recommended, more and more, that you run anti-virus on ALL machines you have. There's just too much stuff running around out there. But putting this on a SQL Server creates some interesting issues. Our resident security guru, Brian Kelley, looks at some of the things you need to consider when deploying anti-virus products on your servers.
2004-05-13
23,816 reads
Good enough for your bookshelf? This one meets that requirement for Brian, click the link to find out why.
2004-04-13
8,904 reads
Brian has been busy lately helping us with content for our magazine (you have checked out www.sqlserverstandard.com haven't you?) but he's back this week with a great write up a new product that let's you read from the transaction log.
2004-02-18
10,828 reads
Brian writes regularly for us on sql security issues, this week he discusses the pros and cons of various authentication methods.
2003-08-14
18,157 reads
Regular columnist Brian Kelley reviews the real world impact that inadequate security can have by reviewing some recent incidents in the sql/security world. Very much worth reading, especially if you have credit card data.
2003-07-31
7,537 reads
As we mentioned before, Brian will be writing a column covering all facets of security. Turns out that there is so much to cover, he has agreed to write two columns per month! This article talks about the principle least privilege, why it doesn't always work, and some good info about removing the Builtin\Admin account.
2003-06-27
21,138 reads
Brian will be writing a monthly column for us on SQL Security, definitely a hot topic these days! He starts off by discussing the need for a built in db_executor role and how to grant permissions manually to achieve the same effect. Terrific concept, as granting table access can lead to bad things! If there is a security topic you'd like to see more info on, post a note to the article or email us at articles@sqlservercentral.com.
2003-05-16
41,255 reads
Brian spends a lot of time in our forums helping out. Based on a recent question from a reader he put together some tips he used when he was preparing for the MCSE exams. Interesting reading!
2003-04-30
9,895 reads
SQL Server 2025 introduces native support for vector data types and external AI models....
By Steve Jones
Fear is fueled by a lack of imagination. The antidote to fear is not...
The slidedeck and the SQL scripts for the session Indexing for Dummies can be...
I'm building ETL packages in SSIS. My data comes from an OLE DB Source...
Comments posted to this topic are about the item Building AI Governance and Policies-...
Why is sql doing a full scan VS seeking on the index? I've included...
The DBCC CHECKIDENT command is used when working with identity values. I have a table with 10 rows in it that looks like this:
TravelLogID CityID StartDate EndDate 1 1 2025-01-11 2025-01-16 2 2 2025-01-11 2025-01-16 3 3 2025-01-11 2025-01-16 4 4 2025-01-11 2025-01-16 5 5 2025-01-11 2025-01-16 6 6 2025-01-11 2025-01-16 7 7 2025-01-11 2025-01-16 8 8 2025-01-11 2025-01-16 9 9 2025-01-11 2025-01-16 10 10 2025-01-11 2025-01-16The docs for DBCC CHECKIDENT say this if I run with only the table parameter: "If the current identity value for a table is less than the maximum identity value stored in the identity column, it is reset using the maximum value in the identity column. " I run this code:
DELETE dbo.TravelLog WHERE TravelLogID >= 9
GO
DBCC CHECKIDENT(TravelLog, RESEED)
GO
INSERT dbo.TravelLog
(
CityID,
StartDate,
EndDate
)
VALUES
(4, '2025-09-14', '2025-09-17')
GO
What is the identity value for the new row inserted by the insert statement above? See possible answers