Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««12345»»

SSIS & Environment Variables Expand / Collapse
Author
Message
Posted Wednesday, March 13, 2013 8:32 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, May 14, 2014 11:39 AM
Points: 26, Visits: 59
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.
Post #1430431
Posted Wednesday, March 13, 2013 10:49 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, May 14, 2014 11:39 AM
Points: 26, Visits: 59
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
------------------------------
Post #1430527
Posted Wednesday, March 13, 2013 10:49 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, May 14, 2014 11:39 AM
Points: 26, Visits: 59
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
------------------------------
Post #1430528
Posted Wednesday, March 13, 2013 11:16 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 9:36 AM
Points: 5,230, Visits: 9,455
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
Post #1430760
Posted Friday, March 15, 2013 1:16 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, March 19, 2013 11:32 AM
Points: 3, Visits: 10
If the job is run by SQL agent. Restart SQL agent. The altered env var will then get picked up.
Post #1431381
Posted Friday, March 15, 2013 2:39 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 9:36 AM
Points: 5,230, Visits: 9,455
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
Post #1431407
Posted Friday, March 15, 2013 12:58 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, May 14, 2014 11:39 AM
Points: 26, Visits: 59
Ok Got it.Thanks.
Post #1431691
Posted Monday, March 18, 2013 3:24 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, May 14, 2014 11:39 AM
Points: 26, Visits: 59
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
Post #1432364
Posted Monday, March 18, 2013 5:00 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, March 19, 2013 11:32 AM
Points: 3, 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
Post #1432401
Posted Monday, March 18, 2013 5:15 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, May 14, 2014 11:39 AM
Points: 26, Visits: 59
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.


Post #1432404
« Prev Topic | Next Topic »

Add to briefcase «««12345»»

Permissions Expand / Collapse