August 16, 2018 at 4:32 am
Hello
Using SQL 2008 R2
We have around 300 packages all stored in one specific folder
Is there an easy way to list the databases that each package connects to?
I'm trying to establish database dependencies for each package without going into each one in turn
There seems to be a few 3rd party tools around for this
Some that look to provide excellent in-depth analysis
All look to come at a cost
I'm only after the basics in this instance
Thanks
- Damian
August 16, 2018 at 7:28 am
Outside of loading those packages into an XML column and then parsing the XML using T-SQL, I'm figuring you would need to use VBScript or VBA to parse each file.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
August 16, 2018 at 8:55 am
are the packages using dtsconfig files, or do they all use embedded connection managers?
either way, you can use an SSIS package and some script tasks to scan for substrings of the dtsx/dtsconfig files.
I've done exactly that for scanning those files and rdl files too;
My technique relied heavily on letting SQL do the searches, so the package was just a data gathering device.
I stuck all the text from the files(dtsx/dtsconfig/rdl) into a SQL table, so that i could cross apply a version of DelimitedSplit on them to spit on find '<commandText' ,'Data Source= and other strings so i could find each instance of what i was looking for.
mine was just a foreach file loop that read each file into a string , inserted that string into a table, and then a few procedures post loading that parsed out that table.
Lowell
August 17, 2018 at 8:48 am
Thanks, a package with a loop seems like a sensible option
So literally read everything in and use SQL to handle the database name extraction
- Damian
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply