Simple Steps to Creating SSIS Package Configuration File

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by Lanre Famuyide » Simple Steps to Creating SSIS Package...

25 posts, Page 3 of 3

«««1 2 3

Simple Steps to Creating SSIS Package Configuration File

Rate Topic

Display Mode

Topic Options

Author

Message

Famson

Posted Monday, May 18, 2009 10:00 AM

SSC Rookie

Group: General Forum Members
Last Login: Friday, January 18, 2013 2:00 PM
Points: 35, Visits: 163

Nice input Lempster, storing configuration settings in a table makes it possible to set very granular permissions. But configuration files in XML format can also be secured using Access Control List (ACL) on the operating system.

Although this does not provide the granular permission setting as available in a table, however, it secures the xml configuration file and protects it from unauthorized access.

Cheers!

Post #719208

Lempster

Posted Monday, May 18, 2009 10:15 AM

UDP Broadcaster

Group: General Forum Members
Last Login: Tuesday, May 21, 2013 8:40 AM
Points: 1,450, Visits: 760

True, but permissions to tables should be under exclusive control of DBAs whereas ACL could be changed by IT Ops/Domain Admins etc.

Post #719230

Famson

Posted Monday, May 18, 2009 10:28 AM

SSC Rookie

Group: General Forum Members
Last Login: Friday, January 18, 2013 2:00 PM
Points: 35, Visits: 163

That's true, I assumed the database server is under the control of the DBA and any change is subject to a proper change control process.

But I sure agree with you that in an environment where the Systems Admins and other Operations staff can effect changes at anytime, then using a table seem perfect. Smile

Post #719242

hennie7863

Posted Wednesday, May 19, 2010 7:18 AM

SSC Rookie

Group: General Forum Members
Last Login: Wednesday, April 24, 2013 12:41 AM
Points: 44, Visits: 3,321

In my projects sofar i've have created configuration files in my packages. I made one development folder and a production folder. In this case i only have to pass the production folder to the next machine in the DTAP process (in theory). And, i thought that MS advised to do this like this. Build in a development environment deploy somewhere else. Even Jamie Thompson best practices says you should put the configuration in the projectfolder (so i did).

Now i've some interesting (in either case for me). the package configuration file is 'connected' in the development environement in the package. When i want to deploy it to the production folder i do a built (bin) and copy it to production folder. But what do i do with the configuration file?

Currently, i point my configurationfile to the production folder but that, i would say, is not very neat. building the package in a development folder, pinpointing to production folder and having a production folder. Am i thinking wrong or what?

Or should i integrate the development folder in the production (project) folder?

Greetz,
Hennie

Post #924279

vani_r14

Posted Tuesday, December 14, 2010 3:33 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, May 06, 2013 10:48 PM
Points: 123, Visits: 399

Hi there

I think for a novice like me this is very useful, however in the part when adding the file to configuration a comment would be quite helpful (if there is no config file already you can create one here or to that extent)...

Cheers

Post #1034819

« Prev Topic | Next Topic »

25 posts, Page 3 of 3

«««1 2 3

Permissions