The Studio commonly utilizes another type of variable – a context variable. Context variables allow jobs to be executed in different ways, with different parameters.
A classic example of this is when we develop a job and want to run it in different environments – development, test, and production, for example. Let us suppose that our job has to connect to a database, and, as is common, the connection details for development, test, and production databases are different. We could create three copies of the job, each one with different connection details configured, but this duplicates code and makes job maintenance more difficult. Far better would be to create a single job and allow it to run with different connection details depending upon the database you want to target at any given time. The Studio context solves this problem.
Contexts are user-defined variables that can be invoked at runtime and there are three ways that we can implement context variables – embedded variables,...