We use DI 4.6 version and the number of jobs modified/newly developed would be migrated between Dev, SIT and Prod. Most of the times, we have to take individual jobs as .spk  export and import the same in the next environment. Sometimes, bigger packages have to be imported one by one at job/ table level and its painfull task.   When it comes to migration of jobs, some of them would be small and some would be bigger, time taken is more in the import and the export to be more precise. Re-deployment does not take much time to what ws observed.   Overall, I feel the time is taken when there is a communication made between Windows machine and the Server, When its already in the UNIX server, why bring them to Windows machine as a package and import it back to UNIX server using DI? Hope Batch does not involve windows.   So how do we do the same in batch interface? Would like to know how and if this could improve performance, would be bigger achievement. ... View more