While you might be able to, I would not advise it. The Pro/INTRALINK DB can
be quickly exported to a test system and able to be rehosted very easily.
Remember also, that for your first few test migrations, you don't have to do
the actual Pro/ENGINEER content. Make sure all of you key information
migrates properly, they do the actual file migration portion. If you run
into issues, rehosting can be done in a matter of minutes vs. trying to
debug it if it fails on another migration. This is why VMware (in ranks up
there with like fire and sliced bread) is such an excellent tool for these
situations. Once you have a copy of your Production instance on VMware, you
can snapshot it and then proceed with your test migrations. Simply go back
to the snapshot for a fresh copy of your Production environment. I have
saved many man hours of work using this method at other clients.
On Sat, Apr 12, 2008 at 5:40 PM, Ravi Sankaran <email@example.com>
> We are in the process of migrating Pro*I 3.4 data to PDMLink 8.0 (m045. We
> were able to successfully perform one migration)…lets say to DEV. Can we use
> the same Pro*I database for migration to a fresh PDMLink system…say TST?
> Should we run the clean up scripts after the proI database is hooked to the
> PDMLink TST system? Any thoughts/pointers will be appreciated.