We are just starting to use replication.
Some of the features in our application dynamically create database objects (stored procs, views, etc) on the publisher that need to be immediately cataloged on the subscriber.
To solve this problem, I have created a DDL Trigger on the publisher that calls a stored proc on the subscriber with the SQL statement that was just executed. The stored proc on the subscriber calls sp_executeSQL with the SQL statement and the object is created (dropped, altered) on the subscriber.
This approach works fine in a test environment.
Is anyone using this approach in production?
Am I abusing DDL Triggers (using them in a way that is not intended)?
Is there a better way?
TIA for your help
-Pat
P.S. We having problems getting to work on clustered servers, but I assume that is related to configuration rather than the approach.