I'm blowing off the dust on BMC Migrator. It has been years since I've messed with it. I've used it in the past to migrate small amounts of code from dev to test to production. What I'm looking at now is using it as a sync tool between the environments for code only. I've usually just done a database backup and restore in the past and for small code migrations I just export/import .def files. There are definitely pros/cons to all these methods. My plan now is to use RRRChive to migrate data updates and BMC Migrator to do code migration. This will give me much more control then a simple database backup and restore. Is anyone currently taking this approach between dev/test/prod. We're using MS SQL 2012 on the backend, which I'll use database replication between prod and coop.
Brian DISCLAIMER: The information contained in this e-mail and its attachments contain confidential information belonging to the sender, which is legally privileged. The information is intended only for the use of the recipient(s) named above. If you are not the intended recipient, you are notified that any disclosure, copying, distribution or action in reliance upon the contents of the information transmitted is strictly prohibited. If you have received this information in error, please delete it immediately. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"