SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


$Project varialbes?


$Project varialbes?

Author
Message
gbritton1
gbritton1
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1339 Visits: 879
I'm following a course in SSIS from PluralSight. In one module, an Execute Package task references a variable in the parent task like this:

@[$Project::foo]

where "foo" is a Project variable (new with SQL Server 2012)

I'd like to know:

1. Is this usage documented somewhere?
2. are there other variable groups that can/must be accessed with the "$" format? e.g. can I refer to varialbes with names like @[$Package::Name] or @[$Parent::Name]?

I'm looking for some reference docs on this.
jason.freier
jason.freier
SSC Rookie
SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)

Group: General Forum Members
Points: 46 Visits: 168
There's quite a bit of documentation in books online, as well as blog posts on using the new features in 2012 SSIS.
The $ sign is a new addition for accessing project and package scoped parameters.
Variables, which existed before parameters, are accessed via @[User::<variablename>] and can have package, control flow, or even task level scoping.

Accessing a project level parameter:
@[$Project::<parameter_name>]

Accessing a package level parameter:
@[$Package::<parameter_name>]

Lots of beneficial uses as long as you are willing to go the route of project deployments and not atomic package deployments.
I.E. use a project level parameter for your connection strings for your project connection managers and you no longer have to worry about changing them in each package. Just add the project connection manager once to a package in a project, right click it and select parameterize and specify your project parameter and that's it. Now when you use it in other packages, it's already configured.

Also very useful for dynamically setting working directories for separating out your log files, raw files, and pending and processed files.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search