I'm wondering what the best practice is for publishing jobs in DTAP? If you create jobs, should you base all local values like hosts, database names etc. on variables and use these to adapt jobs at runtime to their environment? Or is it better to use connections per server with the same name but pointing to another host?

I'd like to keep myself from reinventing the weel. Many current users will probably develop jobs on a development server and publish them through some sort of test and acceptance procedure before putting them in production?

What is DTAP? Do you have any link to information about that?

---

What is DTAP? Do you have any link to information about that?

It simply means Development, Test, Acceptance, Production. New software/configs etc are created on a Development server, tested on the Test server then proposed for acceptance on the Acceptance server before deployment on the Production server. (Also see this page on wikipedia )

So, I'd need to create jobs in such a way that they can created on D and then cloned to the T,A and P server with minimal to no changes, by using variables and/or connections that can have a different content on every DTAP server.

I discovered that using equally named variables on every server work fine when cloning jobs using such a variable, but Connections, even when using the same name are not reused. So connections always need to be reset after cloning. Would be nice if connections would change dynamically too.

I see. Basically you can use User Variables which are global and update these when exporting these after exporting settings.

---