April 13, 2017 at 9:30 am
My company provides client with software that uses SQL for the backend. My latest project is to create an SSIS project that will be installed and run at client locations. Parameters are loaded and the package is run from the application. Everything works,or so it seems (so far). My question;
How much development information (such as who, PCID, Server, Location) can be removed from the xml files before I distribute this to clients.
Thanks.
April 13, 2017 at 10:40 am
Budd - Thursday, April 13, 2017 9:30 AMMy company provides client with software that uses SQL for the backend. My latest project is to create an SSIS project that will be installed and run at client locations. Parameters are loaded and the package is run from the application. Everything works,or so it seems (so far). My question;
How much development information (such as who, PCID, Server, Location) can be removed from the xml files before I distribute this to clients.Thanks.
If you use an SSIS Configuration database, you can have none of it present. Everything it needs could be loaded from the configuration table. Typically, folks use the project property "Don't Save Sensitive" to ensure that passwords and id's for connection managers are not saved with the package, so having the config db is the easiest way to allow yourself the freedom to use that option.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
April 13, 2017 at 10:50 am
There is also stuff like this
DTS:CreationDate="2/17/2016 10:19:04 AM"
DTS:CreatorComputerName="Brad"
DTS:CreatorName="Wile E Coyote"
Which I'm not sure can be modified through the GUI, though can be changed via a direct edit of the XML.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply