April 9, 2013 at 1:16 am
Hi,
Does anyone have where trace flag 8295 is used for. I found it active on a customer server, SQL Server 2008 R2 SP2 Enterprise Edition, but I can't figure out the purpose of it. When I search the internet, nobody seems to know this trace flag.
Can anyone help me?
Regards
Pieter
April 9, 2013 at 2:56 am
Looks like it is SCCM 2012 installation that is adding 2 trace flags onto the SQL Server during installation...
Still, what is it used for 🙂 ?
Regards
Pieter
November 20, 2014 at 10:37 am
I know this is an old post but just in case you still want to know:
'Creates a secondary index on the identifying columns on the change tracking side table at enable time'. This allows creation of a secondary index for changetracking tables, which we heavily use for replication between Configuration Manager sites.
http://blogs.technet.com/b/smartinez/archive/2013/03/06/sql-for-configmgr-2012.aspx
April 12, 2015 at 9:45 pm
The reasoning behind this is that Change Tracking by default assumes you'll want CT info for everything in the underlying table. This trace flag causes an index to be built for when you only want to pick up changes for a subset of the data; the assumption being that you can identify this data via the primary key.
A real-world example: you are tracking changes for your customer table but only want to extract those changes on a customer by customer basis
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply