Re: RE: Copy PROD to DEV
There are 3 ways I have used to accomplish this when Central Objects are on the SQL Server.
1) Use R98403. There is a version set to copy Central Objects from one path code to another.
Pro: JDE supported
Con: This takes forever. R98403 uses the JDE copy table, which goes record-by-record. When you've got F98741 tables running over 2 million records, you're talking about an all day affair.
2) Empty all Central Object tables in the target path code. Use SQL Query Ananlyzer to Insert into (target) select * from (source) for each table.
Pro: Much faster than #1, usually taking about 4 hours, depending on your database server and how many records you've got.
Con: There is a better way to accomplish the same thing.
3) Use a SQL Server tool like BCP (bulk copy) to accomplish the same taks as #2. You still have to empty the tables first, but then you can use BCP to do the rest.
Pro: Fastest method of the 3, should take no more than 2 hours unless your database server is low on resources.
Con: You need to know SQL Server command line tools. You need space to hold the database dump files that BCP will generate.
There is an additional consideration. If you use #1, you don't have to worry about any path code specific data in any of the Central Object tables. If you use #2 or #3, and F983051 is in your SQL database, then you have to worry about changing all the references from PRODB733 to DEVB733.
Besides speed, the other thing in #3's favor is that JDE even supplies some of the tools to do the job. If you look at the DATABASE directory under B7332 of your Deployment Server, you will see the batch files you used when you loaded Central Objects in the first place. All it takes is a little rewrite to accomplish the task. I have attached a small zip file with something I've used in the past. Unzip the files into the same place where JDEBCPIN.BAT is located on your Deployment Server. Then make sure your Deployment Server has the space to hold the results. You might also want to move the existing .DTA files out of the way in anticipation of the creation of the new ones. Lastly, check the batch files to make sure you are only doing this for the tables that exist in your database.
Your mileage may vary ...