Is it possible to use Change Tracking on a Replication target? We have a setup where the production SQL Server databases are replicated to an offsite location using SQL Server Replication (transactional replication).

I am looking at using SQL Server Change Tracking to get the updated data in order to perform some processing and add values to a cache. Before I start down this road, does anyone know if it's possible to use Change Tracking on a replication target? It seems like it should work, but it also seems complex enough that there would be gotchas.
does anyone know if it's possible to use Change Tracking on a replication target?


When you say replication target, do you mean subscriber ? Irrespective, of it, CT will work with replication.



Things to consider when implementing Change Tracking (CT):


Make sure you have retention &amp; clean up of the data in the hidden CT tables.
Enable CT on the tables that you need. Dont go haywire and enable it on all the tables in the database.
Read carefully the article written by Kendra - Performance Tuning SQL Server Change Tracking