<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The SQL Server default trace</title>
	<atom:link href="http://www.eraofdata.com/blog/the-sql-server-default-trace/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eraofdata.com/blog/the-sql-server-default-trace/</link>
	<description>SQL Server posts that DBAs will (hopefully) find useful.</description>
	<lastBuildDate>Fri, 04 May 2012 18:56:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Ajmer Dhariwal</title>
		<link>http://www.eraofdata.com/blog/the-sql-server-default-trace/#comment-4106</link>
		<dc:creator>Ajmer Dhariwal</dc:creator>
		<pubDate>Wed, 21 Dec 2011 22:20:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=161#comment-4106</guid>
		<description>This was covered in the last query example (Query 5a: Isolating who made server configuration changes). Just run that and it will show you who did it, as long as it was in the trace file(s) you are interrogating.
Thanks for asking the question as it higlighted some strange formatting in this post which I&#039;ve tried to tidy up in order to make it clearer.</description>
		<content:encoded><![CDATA[<p>This was covered in the last query example (Query 5a: Isolating who made server configuration changes). Just run that and it will show you who did it, as long as it was in the trace file(s) you are interrogating.<br />
Thanks for asking the question as it higlighted some strange formatting in this post which I&#8217;ve tried to tidy up in order to make it clearer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Parvinder</title>
		<link>http://www.eraofdata.com/blog/the-sql-server-default-trace/#comment-4105</link>
		<dc:creator>Parvinder</dc:creator>
		<pubDate>Wed, 21 Dec 2011 12:34:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=161#comment-4105</guid>
		<description>Is there way to see who &amp; when changed the SQL server configuration setting from default trace? 
setting Like max degree of parallelism, MIN/MAX Memory, Enable/Disable AWE..etc..  


Thanks in advance.</description>
		<content:encoded><![CDATA[<p>Is there way to see who &amp; when changed the SQL server configuration setting from default trace?<br />
setting Like max degree of parallelism, MIN/MAX Memory, Enable/Disable AWE..etc..  </p>
<p>Thanks in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GT</title>
		<link>http://www.eraofdata.com/blog/the-sql-server-default-trace/#comment-3674</link>
		<dc:creator>GT</dc:creator>
		<pubDate>Wed, 05 Oct 2011 21:00:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=161#comment-3674</guid>
		<description>Excellent post. Thank you!</description>
		<content:encoded><![CDATA[<p>Excellent post. Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajmer Dhariwal</title>
		<link>http://www.eraofdata.com/blog/the-sql-server-default-trace/#comment-3453</link>
		<dc:creator>Ajmer Dhariwal</dc:creator>
		<pubDate>Wed, 31 Aug 2011 22:10:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=161#comment-3453</guid>
		<description>The default trace is deliberately designed to be too light-weight to delve into alterations to specific rows, so your best bet is create a specific trace filtered on the msdb database and the specific tables (msdb.dbo.sysjobhistory) concerned. Make sure it&#039;s capturing columns like clientprocessid, as well as hostname and loginname, nt_username, applicationname etc.
Before you run the trace, right click on SQL Server Agent, go to Properties, and click on the History tab and review the settings there for history retention.</description>
		<content:encoded><![CDATA[<p>The default trace is deliberately designed to be too light-weight to delve into alterations to specific rows, so your best bet is create a specific trace filtered on the msdb database and the specific tables (msdb.dbo.sysjobhistory) concerned. Make sure it&#8217;s capturing columns like clientprocessid, as well as hostname and loginname, nt_username, applicationname etc.<br />
Before you run the trace, right click on SQL Server Agent, go to Properties, and click on the History tab and review the settings there for history retention.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://www.eraofdata.com/blog/the-sql-server-default-trace/#comment-3452</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Wed, 31 Aug 2011 17:28:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=161#comment-3452</guid>
		<description>Is there a way to see who or what deleted data from a system table? I&#039;ve got job history vanishing on one insstance and I&#039;ve checked all the obvious settings - nothing should be deleting this data. I&#039;d like to run a trace on the job history table and see what is removing the data.</description>
		<content:encoded><![CDATA[<p>Is there a way to see who or what deleted data from a system table? I&#8217;ve got job history vanishing on one insstance and I&#8217;ve checked all the obvious settings &#8211; nothing should be deleting this data. I&#8217;d like to run a trace on the job history table and see what is removing the data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://www.eraofdata.com/blog/the-sql-server-default-trace/#comment-3226</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Tue, 24 May 2011 14:37:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=161#comment-3226</guid>
		<description>Here is a good set of reports for the Default Trace: http://sqlconcept.com/default-trace-audit-documentation-and-faq/</description>
		<content:encoded><![CDATA[<p>Here is a good set of reports for the Default Trace: <a href="http://sqlconcept.com/default-trace-audit-documentation-and-faq/" rel="nofollow">http://sqlconcept.com/default-trace-audit-documentation-and-faq/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Troubleshooting SQL Server login failures (18456 errors)</title>
		<link>http://www.eraofdata.com/blog/the-sql-server-default-trace/#comment-2660</link>
		<dc:creator>Troubleshooting SQL Server login failures (18456 errors)</dc:creator>
		<pubDate>Wed, 09 Feb 2011 19:40:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=161#comment-2660</guid>
		<description>[...] in an out-of-the-box installation) then you don&#8217;t need to start a new trace; check out my SQL Server default trace post [...]</description>
		<content:encoded><![CDATA[<p>[...] in an out-of-the-box installation) then you don&#8217;t need to start a new trace; check out my SQL Server default trace post [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Is there any way to see who deleted a view?</title>
		<link>http://www.eraofdata.com/blog/the-sql-server-default-trace/#comment-2466</link>
		<dc:creator>Is there any way to see who deleted a view?</dc:creator>
		<pubDate>Mon, 22 Nov 2010 07:24:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=161#comment-2466</guid>
		<description>[...] you are on SQL Server 2005 and above you can interrogate the default trace to see what [...]</description>
		<content:encoded><![CDATA[<p>[...] you are on SQL Server 2005 and above you can interrogate the default trace to see what [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Определение источника ошибки авторизации SQL Server (18456 ошибка) at Александр Горбач</title>
		<link>http://www.eraofdata.com/blog/the-sql-server-default-trace/#comment-2460</link>
		<dc:creator>Определение источника ошибки авторизации SQL Server (18456 ошибка) at Александр Горбач</dc:creator>
		<pubDate>Fri, 06 Aug 2010 05:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=161#comment-2460</guid>
		<description>[...] Если Вы используете SQL Server 2005 или выше т у Вас до сих пор включен трассировщик по умолчанию (который включен по умолчанию в установке из коробки), тогда вам не нужна начинать новую трассировку. Проверьте вместо этого мою запись The SQL Server default trace. [...]</description>
		<content:encoded><![CDATA[<p>[...] Если Вы используете SQL Server 2005 или выше т у Вас до сих пор включен трассировщик по умолчанию (который включен по умолчанию в установке из коробки), тогда вам не нужна начинать новую трассировку. Проверьте вместо этого мою запись The SQL Server default trace. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: califguy4christ</title>
		<link>http://www.eraofdata.com/blog/the-sql-server-default-trace/#comment-2442</link>
		<dc:creator>califguy4christ</dc:creator>
		<pubDate>Mon, 26 Oct 2009 20:34:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=161#comment-2442</guid>
		<description>Great post!  Thanks for enumerating a few scenarios, too.</description>
		<content:encoded><![CDATA[<p>Great post!  Thanks for enumerating a few scenarios, too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

