February 27, 2014 at 8:56 am
Hi,
I want to install the SSIS Service on a special server (SSIS Execution Server). On this Server should not run the database engine. This Server should only start the execution of the SSIS packages, which are saved on a different Server (Catalog Server). For that reason I had to connect and access a SSIS Catalog on another Server, because they stored there. The connection from the execution server to the catalog server already works. I have changed the configuration file 'MsDtsSrvr.ini' on the SSIS Execution Server and after restart the SSIS Service, I can see the connection in the activity monitor of the catalog Server. The problem is now, the Connection is made to the msdb database. We didn't use this database for storing the SSIS packages. For that reason, we have es special SSIS database in which the SSIS packages are stored.
In which way I had to configure the SSIS Server (execution or catalog), that it uses this special SSIS database and not the msdb database.
February 27, 2014 at 9:58 am
How are you executing packages on the SSIS execution server ..
--
SQLBuddy
February 28, 2014 at 12:16 am
with T-SQL Statement. I plan to create a CMD Job, which calls the Programm SQLCMD and then start a T-SQL Skript which starts the SSIS Package. The CMD Skript is executed by a Job Scheduler (Not SQL Server Agent).
February 28, 2014 at 12:22 am
Are you using the package or project deployment model?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
February 28, 2014 at 3:36 am
We use project deployment.
February 28, 2014 at 3:46 am
With project deployment, you cannot use the MSDB database and the SSIS service.
You need to install a database engine and enable the SSIS catalog (which creates the SSISDB database).
You can schedule the package on another server. In other words, the scheduling software can run on another server, but the packages themselves will stay in the SSIS Catalog and they will be executed there.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
February 28, 2014 at 6:48 am
elmar.fecker (2/28/2014)
with T-SQL Statement. I plan to create a CMD Job, which calls the Programm SQLCMD and then start a T-SQL Skript which starts the SSIS Package. The CMD Skript is executed by a Job Scheduler (Not SQL Server Agent).
I found it easier to build a .Net executable to accept the command from our enterprise job scheduler and run the appropriate SSIS package.
http://ericeyster.wordpress.com/category/sql-server/ssis-framework/
February 28, 2014 at 11:52 am
elmar.fecker (2/28/2014)
with T-SQL Statement. I plan to create a CMD Job, which calls the Programm SQLCMD and then start a T-SQL Skript which starts the SSIS Package. The CMD Skript is executed by a Job Scheduler (Not SQL Server Agent).
You can use the built-in stored proc to execute packages in SSIS DB ..
--
SQLBuddy
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply