Excelent article, Roy.

I'm thinking that one of the ideal business solutions to use CT is for database synchronization from mobile devices or off-site databases.

To help CT become more "auditable", maybe we could use the syntax:

WITH CHANGE_TRACKING_CONTEXT(@context)

--<INSERT or UPDATE command here>

and send some information about the username or changes inside the @context VARBINARY(128) column. Is there a limitation for using the CT context and would it also become a major pain to maintain like described in the article?

Change Tracking comes with all SQL Server editions so it's a great little feature to have at our disposal. 🙂

Best regards,