Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums  SQL Server 2000 Forums  Import/Export (DTS) and Replication (2000)  Replicating proc,trigger,table changes

Author  Topic  cajun Starting Member 1 Post Posted - 2004-06-15 : 10:24:23 Sql 2000 running on Win 2000 SP4. I have a situation where we have production environments which are replicated to report servers for reporting etc. The issues begin when we apply updates to the production environments. These environments are owned by us and we write the updates etc. Currently we create packaged releases and hand them over to our sysadmin group and they are responsible for applying them. I just think there has to be an easier way to deal with replication than we are doing now. What would be the easiest way to have the report server updated to stay in sync with the production server? I am being told that there is not a way in SQL server to replicate procs, triggers, views etc. Are there any easy ways around this besides unpublishing and republishing the tables affected and then applying the new procs etc to the report server. Currently the scripts we write can contain new tables, table changes, procs, triggers, views etc. This makes it a manual process for the sysadmin group because they can't just run these scripts against the report server due to the fact that they are currently letting replication take care of the tables by unpublishing them and republishing them. Once this is done could the db scripts still be run against the report server and be ok? Maybe we should create scripts seperate for actions that affect rep and actions that do not affect rep. That way they could just run the scripts (something like no_rep_affect.sql) against the report servers and all should be well? Thoughts?