Consider change tracking as an optimization to CDC queries

SQL Server provides a change tacking that should allow us to get infoirmation which changes has changed and thus query only change tables of modified tables. Before more detailed work we need to

• verify if CDC and CT can be both enabled in parallel
• Can we use it when snapshot isolation is not available?

  To overcome the previously listed challenges, we recommend that you use snapshot isolation. This will help to ensure consistency of change information and avoid race conditions that are related to the background cleanup task. If you do not use snapshot transactions, developing an application that uses change tracking could require significantly more effort.

• Is it really an optimization? Does not it query all chnage tables internally?
• Is there a conversion/relation between LSN and synchrnization version?