March 22, 2012 at 2:33 pm
My requirement is pretty simple. I need to develop a SSIS pacakge in which i need to read the data from SQL server 2005 database table and writes into flatfile. Only thing is "flatfile has to be placed in the application server".
Now I want to know the best practises to develop this package.
I assume the problem can come up
1) when the package moved from one environment to another.
2) Access issues
3) What kind of permissions does the sql local account id needs on app server?
Any other issues that can come up..
--Jus
March 22, 2012 at 3:21 pm
This is very general, is it safe to assume you are just starting out using SSIS? This series is great, and has been helpful Stairway to Integration Services[/url]
NewBeeSQL (3/22/2012)
My requirement is pretty simple. I need to develop a SSIS pacakge in which i need to read the data from SQL server 2005 database table and writes into flatfile. Only thing is "flatfile has to be placed in the application server".Now I want to know the best practises to develop this package.
I assume the problem can come up
1) when the package moved from one environment to another.
Look into using Package Configurations. I prefer using either XML configuration files or SQL Server tables to store my configuration data.
2) Access issues
Make sure the account running the SSIS package has access to all resources the SSIS package requires. If running it through SQL Agent, and the job is owned by a sysadmin (e.g. sa, recommended) then the SSIS package will be executed in the context of the SQL Agent service account. If that is not convenient, look into setting up a SQL Agent proxy account.
3) What kind of permissions does the sql local account id needs on app server?
Basically anything the SSIS package does, the executing account will need access to. See item 2.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 23, 2012 at 12:46 pm
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply