BIDev Studio Merging 2 SSIS packages in to one

Hi,

I am new to the product and have set up an intergration service comprising of two seperate ssis packages. At present as far as i know I have to execute them one at a time. Is there any way of performing a single execute to run them both or alternatively merging them into a single package.

Any help would be greatfully appreciated.

Chris

Chris, there is an "Execute Package" task in SSIS that should do the trick for you... Just place two on the control flow and point to the packages you currently have.

You could also merge them into one package, but I have not tried to copy/paste tasks/flows from one package into another...

|||

Thanks Dan

The Execute Package works a treat.

Chris

BIDev Studio Merging 2 SSIS packages in to one

Hi,

I am new to the product and have set up an intergration service comprising of two seperate ssis packages. At present as far as i know I have to execute them one at a time. Is there any way of performing a single execute to run them both or alternatively merging them into a single package.

Any help would be greatfully appreciated.

Chris

Chris, there is an "Execute Package" task in SSIS that should do the trick for you... Just place two on the control flow and point to the packages you currently have.

You could also merge them into one package, but I have not tried to copy/paste tasks/flows from one package into another...

|||

Thanks Dan

The Execute Package works a treat.

Chris

Best way for a SQL Server Service to Log On to the Local Computer

What's the recommended way for all of the SQL Server Services (database
engine, browser, SSIS...) to Log On to the Local Computer. Should it be the
Local System account or should I specify another account. Usually I set the
Log On during installation and never think about it again but I thought it
was worthwhile specifically asking the question.
Michael HocksteinIt is often a good idea to use a domain account with only the privledges it
needs to do what it has to an no more. Have a look at this site for lots of
security related info:
http://www.microsoft.com/sql/techno...ty/default.mspx
Andrew J. Kelly SQL MVP
"michael" <howlinghound@.nospam.nospam> wrote in message
news:9282F5DE-D413-472C-ACA0-5120BD884757@.microsoft.com...
> What's the recommended way for all of the SQL Server Services (database
> engine, browser, SSIS...) to Log On to the Local Computer. Should it be
> the
> Local System account or should I specify another account. Usually I set
> the
> Log On during installation and never think about it again but I thought it
> was worthwhile specifically asking the question.
>
> --
> Michael Hockstein|||Hi, Michael,
I agree with Andrew. In most cases, it is recommended that you use domain
user account for your SQL Server services since trusted security can be
easily established between computers. The domain users are also easily
managed by Active Directory on Domain Controller. As a server side service,
its startup service account should be stable since some operations like
backing up database, creating database, executing xp_cmdshell and SSIS
packages etc may need more permissions (sysadmin or local administrator).
It is convenient that you just add a domain user to your local
administrators group. When you log on your Windows with any login account,
your SQL Server services related jobs, stored procedures and packages
executions will not be affected.
Please refer to the "Server farm-level accounts" section of this article:
Plan for administrative and service accounts
http://technet2.microsoft.com/Offic...5b6-4a7a-8da0-2
d07639d04a11033.mspx?mfr=true
For now, could you please let us know if you need further assistance on
this issue? If you have any other questions or concerns, please feel free
to let us know. It is always our pleasure to be of assistance.
Sincerely yours,
Charles Wang
Microsoft Online Community Support