Content Repository Transaction Removal

Content Repository is using transactions to keep content usage counters up to date in real time. This causes some SGS deployments to fail when a particular piece of content is required for more than one site at a time and results in unusable database connections causing subsequent deployments to fail as well.

The issue can be resolved by removing the transactions from the content repository code and updating the counters in a separate process that runs periodically and counts the number of sites currently using a particular piece of content using the customization database.