DB Creation: Slave tsacommon database have to be manually updated for replication to work

Since we use the same global tsacommon master database configuration to create all the slave tsacommon databases as well, the slave tsacommon databases have replication triggers and few additional logging tables in them.

For replication to work fine, these triggers and tables need to be removed manually. If this task can be automated by using a different db structure, user will not have to do the task manually.

Attaching the drop trigger and drop tables sql files.