﻿<?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 Content tagged Auditing, Blogs</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Auditing, Blogs posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Auditing changes in Merge Replication</title><description><![CDATA[<p>One trick I have learned from the folks on the Replication Support Team is how to proactively audit data changes...</p>]]></description><guid>http://www.sqlservercentral.com/blogs/sqlrepl/2012/10/10/auditing-changes-in-merge-replication/</guid><pubDate>Wed, 17 Oct 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/blogs/sqlrepl/2012/10/10/auditing-changes-in-merge-replication/</link></item><item><title>SQL Audit 301 – Using Powershell to Manage Audits</title><description><![CDATA[<p>Today we’re going to go over some very basic scripts to create, drop, and copy SQL Audit objects using Powershell...</p>]]></description><guid>http://www.sqlservercentral.com/blogs/cleveland-dba/2012/08/13/sql-audit-301-using-powershell-to-manage-audits/</guid><pubDate>Mon, 20 Aug 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/blogs/cleveland-dba/2012/08/13/sql-audit-301-using-powershell-to-manage-audits/</link></item><item><title>SQL Audit 201 – Creating an Audit Solution</title><description><![CDATA[<p>Welcome back, folks!
Ok so, now that we’ve covered the basics of creating a SQL Audit and viewing the output, let’s...</p>]]></description><guid>http://www.sqlservercentral.com/blogs/cleveland-dba/2012/07/31/sql-audit-201-creating-an-audit-solution/</guid><pubDate>Mon, 06 Aug 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/blogs/cleveland-dba/2012/07/31/sql-audit-201-creating-an-audit-solution/</link></item><item><title>SQL Audit 102 – Reading audit output</title><description><![CDATA[<p>Last time we went over the basics of creating a SQL Audit. Now obviously once you’ve gotten your audit in...</p>]]></description><guid>http://www.sqlservercentral.com/blogs/cleveland-dba/2012/07/16/sql-audit-102-reading-audit-output/</guid><pubDate>Thu, 19 Jul 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/blogs/cleveland-dba/2012/07/16/sql-audit-102-reading-audit-output/</link></item><item><title>SQL Server Login Auditing</title><description><![CDATA[<p>In recent months I have been asked to ensure we are auditing both successful and failed logins, not just failed...</p>]]></description><guid>http://www.sqlservercentral.com/blogs/timradney/2012/01/03/sql-server-login-auditing/</guid><pubDate>Thu, 05 Jan 2012 07:00:00 UT</pubDate><link>http://www.sqlservercentral.com/blogs/timradney/2012/01/03/sql-server-login-auditing/</link></item><item><title>Rant: Is It an Effective Control or Not?</title><description><![CDATA[<p>This is spurred on by a comment a pen tester made. He was referring to a particular technology and said something to the effect of, &quot;What do you expect? It's 30 year-old technology.&quot; I was stunned when the comment was relayed to me. My response...</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/66865/</guid><pubDate>Wed, 13 May 2009 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/66865/</link></item></channel></rss>