﻿<?xml version="1.0" encoding="utf-8"?><rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="2.0"><channel><title>SQLServerCentral.com Articles tagged Other, Security</title><link>http://www.sqlservercentral.com/</link><description>Articles tagged Other, Security posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Easy Auditing a Shared Account</title><description>Despite the major advances made with Profiler in SQL Server 2005, auditing changes isn&amp;#39;t one of the strengths of the product. New author Sergey Pustovit brings us his technique that allows auditing of actions using shared accounts from an application. A few minor code changes, but overall this is a very interesting idea.
</description><guid>http://www.sqlservercentral.com/articles/Security/easyauditingasharedaccount/1953/</guid><pubDate>2005/07/20</pubDate><link>http://www.sqlservercentral.com/articles/Security/easyauditingasharedaccount/1953/</link></item><item><title>Removing NT Administrators as Sysadmins</title><description>By default, all NT administrators of the domain that your SQL Server is installed in, have SA rights in every database. This presents interesting challenge for DBAs, political and technical.  Does your NT administrator group need SA rights to every database?  The answer is no.
</description><guid>http://www.sqlservercentral.com/articles/Security/tipremoveadmin/168/</guid><pubDate>2001/05/25</pubDate><link>http://www.sqlservercentral.com/articles/Security/tipremoveadmin/168/</link></item><item><title>Rants about the sa account!</title><description>Using the sa account in development is just plain dumb. Here are some reasons why!

</description><guid>http://www.sqlservercentral.com/articles/Security/sarant/157/</guid><pubDate>2001/05/08</pubDate><link>http://www.sqlservercentral.com/articles/Security/sarant/157/</link></item></channel></rss>