|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Yesterday @ 6:08 PM
Points: 400,
Visits: 331
|
|
What exactly I want to implement is like this -
I have a file watcher which kicks the SSIS packages when ever a flat file arrives into the Source Folder.
When ever the a new file arrives SSIS packages has to process the file by taking the parameters from the configuration file. (Database name, Servername of the Destination table are in Config file)
Meanwhile, another flat file is placed in the source folder and another instance of the same SSIS package needs to be used to process this file.. and so on...
every time the package has to take the parameters from the configuration file.
please help me in solving this issue.
Thanks in advance.
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Tuesday, November 02, 2010 8:28 PM
Points: 73,
Visits: 180
|
|
First let us know below details.
1. how you are activating/running package means, are u using sql job or commandline command or autosys or esp or maestro etc 2. are ur source filenames same all the time? or differs? 3. ...
Each new run of the package will create a new instance, it will use same config file every time, so you can run multiple instances.
if source file name is same then, move file to a working folder and then run ur package
you can run commandline command each time when you see file in source folder...it works in separate process...
RB
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Yesterday @ 6:08 PM
Points: 400,
Visits: 331
|
|
PaVeRa22 (7/9/2010) First let us know below details.
1. how you are activating/running package means, are u using sql job or commandline command or autosys or esp or maestro etc 2. are ur source filenames same all the time? or differs? 3. ...
Each new run of the package will create a new instance, it will use same config file every time, so you can run multiple instances.
if source file name is same then, move file to a working folder and then run ur package
you can run commandline command each time when you see file in source folder...it works in separate process...
RB
1. I am running the SSIS package using SQL agent job. (but I want to run many jobs at the same time which calls the same SSIS package, but the configuration file values should be changed) 2. Every time the source file name is different. (it will have _timestamp) I want to include flat file name and Destination table name (predefined) using configuration file.
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Wednesday, April 24, 2013 12:02 PM
Points: 5,854,
Visits: 4,873
|
|
anand_vanam (7/10/2010) 1. I am running the SSIS package using SQL agent job. (but I want to run many jobs at the same time which calls the same SSIS package, but the configuration file values should be changed) 2. Every time the source file name is different. (it will have _timestamp) I want to include flat file name and Destination table name (predefined) using configuration file.1. Can't, Agent will run a SINGLE instance of a job at a time. 2. The package needs to be smart enough to pick this out.
You might look at: http://www.sqlservercentral.com/articles/Integration+Services+(SSIS)/70346/
CEWII
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Monday, May 20, 2013 12:51 PM
Points: 167,
Visits: 492
|
|
anand_vanam (7/10/2010)
1. I am running the SSIS package using SQL agent job. (but I want to run many jobs at the same time which calls the same SSIS package, but the configuration file values should be changed) 2. Every time the source file name is different. (it will have _timestamp) I want to include flat file name and Destination table name (predefined) using configuration file.
1. You can run the exact same package simultaneously. What you can't do is execute a job while it's currently running. I can set up a job to run package anand_vanam.dtsx. I can set up a second job to run the same package, and they'll run simultaneously. So yes you can run many JOBS which calls the same SSIS Package. 2. It looks like you're looking for a way to execute a package with dynamic parameters. There are many ways to do this. This might be a good start: http://www.mssqltips.com/sqlservertip/1775/different-ways-to-execute-a-sql-server-ssis-package/
|
|
|
|