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,911 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,824 reads
Good enough for your bookshelf? This one meets that requirement for Brian, click the link to find out why.
2004-04-13
8,905 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,840 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,185 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,545 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,144 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,295 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,902 reads
For most DBAs, normalization is an understood concept, a bread and butter bit of knowledge. However, it is not at all unusual to review a database design by a development group for an OLTP (OnLine Transaction Processing) environment and find that the schema chosen is anything but properly normalized. This article by Brian Kelley will give you the core knowledge to data model.
2003-01-13
18,716 reads
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Comments posted to this topic are about the item Where Your Value Separates You...
Comments posted to this topic are about the item Fixing the Error
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:
SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error? See possible answers