The only place I have seen archgid to fail so far is if you have filters using the WEB SERVICE set fields, and if you have changed some of the fields that are mapped in that filter for that set field option. I think it works as designed for most other things it is designed for.
I had brought up this one small oversight with Doug at the past RUG and he said they were aware of it and that it should have been fixed by now but it wasn't at least until version 7.6.04 and its latest patch during the time of the RUG. If it has been addressed now in one of the patches, I am not aware. Joe _____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Jason Miller Sent: Monday, March 03, 2014 9:50 PM To: [email protected] Subject: Re: Database replication to reporting server ** You can use archgid to chance the Schema ID (form ID. https://communities.bmc.com/docs/DOC-19172 I had never tried changing a form ID until I thought about recommending archgid for this thread (but had been meaning to try if for years). In my sandbox I created a form that included an index, ran archgid and all references to the old schemaId were updated to the new schemaId (T/B/H tables and index). One note... Since I changed the schemaId to a number higher than any other form it changed the next schemaId to my number +1. Jason On Mon, Mar 3, 2014 at 1:27 PM, Mike Ilmer <[email protected]> wrote: Hi List, We have the table-based replication of the SQL production database to reporting server. Our DBAs require to provide them the T.. H.. and B.. table information along to the schema name. This works fine for the existing schemas. Replication is the real-time. We have issues with the new tables. In some cases we create remedy form only on the production server, and then a month later getting requirement to add the same form onto reporting server. Setting the table-based replication is an issue because after migration that the table's ID on reporting server (T..,H.., B..) may have the different number. Yes, the best recommendation would be to migrate the new remedy forms to both servers at the same time. Would anybody have the best-practice or the experience recommendation of how to simplify setting of the replication process (for SQL database). For instance replicate the remedy system tables ("arschema", fields, forms, etc.) Thank you, Mike _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
