June 20, 2010 at 6:57 pm
I am considering deployment my SSIS package to SQL Server instead of the file system.
Is msdb the only database that you can deploy the package to?
What are the advantages of using the database instead of the file system?
I have a configuration table on another database (not msdb). Would that cause a problem?
We use Control-M to schedule the running of different items. Can Control-M Work with an SSIS package stored on the server?
June 21, 2010 at 7:04 am
imani_technology (6/20/2010)
What are the advantages of using the database instead of the file system?
I can answer this question. The advantages are that you can use built-in features of SQL Servers, such as security and versioning.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 22, 2010 at 9:50 am
imani_technology (6/20/2010)
I have a configuration table on another database (not msdb). Would that cause a problem?
I can answer this...
Configuration table can be any where, any data base. Connection to the configuration table can be defined in any XML file or Environment Variable
------------------
Why not ?
June 23, 2010 at 6:30 am
imani_technology (6/20/2010)
I am considering deployment my SSIS package to SQL Server instead of the file system.Is msdb the only database that you can deploy the package to?
Yes.
See article
June 23, 2010 at 12:17 pm
Control-M is a scheduler and it cannot schedule the job deployed in SQL Server.
You can use the SQL agent to do the job.
I would suggest you to deploy it on file system for the control-m to schedule it.
I recommend http://www.expertmsbitraining.com
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply