I don't know how many people use .ini files with their DTS packages to set global variables and connection info, but we do it a lot where I work, so I thought I'd pass along how we changed this process when converting to SSIS.
Run the DTS Conversion Wizard to create your package as a .dtsx file (or which ever file type you want). Note, if you do the .dtsx file, you *must* add it to a project/solution in the Business Intelligence Developer Studio before you can use the Package Configurations options.
Disable the Script Task which looks for the .ini file. Go up to the menu and choose SSIS -> Variables. This will populate the variables list which will be pinned to your left (unless you've changed where this docks). Make sure the Control Flow tab is chosen, then right-click in the free space. Navigate to Package Configurations. This will open up a Wizard.
Pass the Wizard's first screen and, on the second screen, choose where you want your config file saved. The PCon Wizard generates an XML configuration file which actually replaces your .ini file. The third screen gives you the properties to export to the XML config file. Choose the items you want in the XML file (if you just randomly click all, it will ALL be in the XML file and you don't really need everything). Mind you, what you need in your config file varies depending on what you're doing, but you should at least choose Name & Value from all the variables plus from your connection info.
Once you've selected what you want in the config file, it shows you what you've selected in a final "info" screen and you just click Finish. Note that if you edit the config file at a future date, it will overwrite your current file, so backup the file someplace if you ever want to go edit it and then decide the changes you made were Very Bad... @=)
Finish updating the rest of your package as appropriate. Then just make sure your config file gets placed on the server with the new SSIS package and you should be set.
I hope this is helpful. If you spot errors in anything I stated, please let me know ASAP. I'm learning this all myself as I go, and we're still in the Development phase of our conversion.
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
Run the DTS Conversion Wizard to create your package as a .dtsx file (or which ever file type you want). Note, if you do the .dtsx file, you *must* add it to a project/solution in the Business Intelligence Developer Studio before you can use the Package Configurations options.
Disable the Script Task which looks for the .ini file. Go up to the menu and choose SSIS -> Variables. This will populate the variables list which will be pinned to your left (unless you've changed where this docks). Make sure the Control Flow tab is chosen, then right-click in the free space. Navigate to Package Configurations. This will open up a Wizard.
Pass the Wizard's first screen and, on the second screen, choose where you want your config file saved. The PCon Wizard generates an XML configuration file which actually replaces your .ini file. The third screen gives you the properties to export to the XML config file. Choose the items you want in the XML file (if you just randomly click all, it will ALL be in the XML file and you don't really need everything). Mind you, what you need in your config file varies depending on what you're doing, but you should at least choose Name & Value from all the variables plus from your connection info.
Once you've selected what you want in the config file, it shows you what you've selected in a final "info" screen and you just click Finish. Note that if you edit the config file at a future date, it will overwrite your current file, so backup the file someplace if you ever want to go edit it and then decide the changes you made were Very Bad... @=)
Finish updating the rest of your package as appropriate. Then just make sure your config file gets placed on the server with the new SSIS package and you should be set.
I hope this is helpful. If you spot errors in anything I stated, please let me know ASAP. I'm learning this all myself as I go, and we're still in the Development phase of our conversion.
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"