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" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
