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


SSIS & Environment Variables


SSIS & Environment Variables

Author
Message
nishav2
nishav2
SSC-Enthusiastic
SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)

Group: General Forum Members
Points: 141 Visits: 103
Jeff,
Yes the connection is named the same(Configuration filter is reused in each package) across all the packages.
I find the error when I click on Edit package configuration.
nishav2
nishav2
SSC-Enthusiastic
SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)

Group: General Forum Members
Points: 141 Visits: 103
Below is the error message I am getting when I try to set up table valued package configuration.I am referring the same configuration filter across all the packages.Since the SOURCE_DB and Destination_DB connection are not in package level I am not able to create the package configuration. This error message is shown after enabling th epackage config and when clicking on 'EDIT' .



TITLE: Microsoft Visual Studio
------------------------------

Some configurations from table "[dbo].[SSIS_Configurations_New]" with configuration name "Master" could not be loaded due to the following reasons:
\Project.Connections[Source_DB].Properties[InitialCatalog]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Source_DB].Properties[InitialCatalog]'.
\Project.Connections[Source_DB].Properties[ConnectionString]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Source_DB].Properties[ConnectionString]'.
\Project.Connections[Destination_DB].Properties[InitialCatalog]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Destination_DB].Properties[InitialCatalog]'.
\Project.Connections[Destination_DB].Properties[ConnectionString]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Destination_DB].Properties[ConnectionString]'.

------------------------------
BUTTONS:

OK
------------------------------
nishav2
nishav2
SSC-Enthusiastic
SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)

Group: General Forum Members
Points: 141 Visits: 103
Below is the error message I am getting when I try to set up table valued package configuration.I am referring the same configuration filter across all the packages.Since the SOURCE_DB and Destination_DB connection are not in package level I am not able to create the package configuration. This error message is shown after enabling th epackage config and when clicking on 'EDIT' .



TITLE: Microsoft Visual Studio
------------------------------

Some configurations from table "[dbo].[SSIS_Configurations_New]" with configuration name "Master" could not be loaded due to the following reasons:
\Project.Connections[Source_DB].Properties[InitialCatalog]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Source_DB].Properties[InitialCatalog]'.
\Project.Connections[Source_DB].Properties[ConnectionString]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Source_DB].Properties[ConnectionString]'.
\Project.Connections[Destination_DB].Properties[InitialCatalog]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Destination_DB].Properties[InitialCatalog]'.
\Project.Connections[Destination_DB].Properties[ConnectionString]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Destination_DB].Properties[ConnectionString]'.

------------------------------
BUTTONS:

OK
------------------------------
John Mitchell-245523
John Mitchell-245523
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14043 Visits: 15946
This is because you're trying to configure things that don't exist in the package. If you're sharing one configuration file (or configuration table) between packages, the packages need to have the same structure, at least to the extent that the paths to all the items being configured are the same.

John
Drndrb
Drndrb
Forum Newbie
Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)

Group: General Forum Members
Points: 7 Visits: 10
If the job is run by SQL agent. Restart SQL agent. The altered env var will then get picked up.
John Mitchell-245523
John Mitchell-245523
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14043 Visits: 15946
Drndrb (3/15/2013)
If the job is run by SQL agent. Restart SQL agent. The altered env var will then get picked up.

No need. He's using a SQL table package configuration, not an environment variable.

John
nishav2
nishav2
SSC-Enthusiastic
SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)

Group: General Forum Members
Points: 141 Visits: 103
Ok Got it.Thanks.
nishav2
nishav2
SSC-Enthusiastic
SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)

Group: General Forum Members
Points: 141 Visits: 103
Hi,

Today I am facing problem when invoking multiple packages from a master package.

Here is the scenario.

Master Package has the below tasks conigured.
- For Each loop container (To loop through a folder for executing all the packages available in that folder)
-Execute Package Task (All the packages are placed in the file system)

Child Package :1
-consist of 3 Execute SQL task (Which is just a insert statement) -This package runs successfully.

Child Package:2
-consist of 2 Execute SQL task (Which is just a insert statement)
First SQL task runs good.
Second SQL task has syntax problem.

I have configured Checkpoint in all these Child packages.In my case -Child PAckage:1 runs successfully.But Child Package :2 fails at the second Execute SQL task.So my checkpoint works good when i do the needed modification.

But the issue is My For EachLoop container executes Child PAckage:1(Which should not happen) and then the Second Execute SQL Task (Which failed in first run).Because of the checkpoint file SSIS is not running the first Execute SQL task in the Chuld Package:2.

Please suggest how to keep track of failed package alone and to restart from that point.

Thanks
Nisha.V
Drndrb
Drndrb
Forum Newbie
Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)

Group: General Forum Members
Points: 7 Visits: 10
Can you not identify whether the rows previously inserted already exist and then do nothing if they do or insert them if they do not. That way you can just restart the packages and not have to worry about restarting from a certain point or inserting duplicate rows.

Check out: http://msdn.microsoft.com/en-us/library/ms140226.aspx

read the section 'Defining Restart Points'

you will see a comment regarding foreach loops
nishav2
nishav2
SSC-Enthusiastic
SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)SSC-Enthusiastic (141 reputation)

Group: General Forum Members
Points: 141 Visits: 103
Yes I can do that.But my concern is I am using "For Each loop" task for executing several child packages (Which makes million of rows to be loaded into the destination table). If I make the check condition (if the row exist or not) for every single package,it would be time consuming and the package may run for indefinite amount of time.So if there is any other way where I can call all the child packages from a master package and also if I could execute the package from the point of failure then that will solve my need.??

Thanks for your reply.
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