August 14, 2009 at 4:50 am
This is probably an impossible idea.
We have a server that's being retired. I'm trying to figure out a way, short of downloading each and every package, of browsing the packages in MSDB to see if a certain connection manager exists in the package or if there's a certain connection string in the packages.
The issue being that there's the possibility someone forgot to throw the connection manager into a config file.
Any thoughts on how this can be accomplished? I've checked the sysdtspackages90 table and there's nothing in there that's helpful.
Comments appreciated. Thanks in advance.
August 14, 2009 at 12:16 pm
Boy, I don't know where it stores them. Seems like it must actually be storing them in the file system somewhere. How about running profiler and deploying a package to MSDB and see what happens?
I tried the obvious sysdts tables, no luck, and my old friend syscomments, also no luck.
Rick Todd
August 17, 2009 at 5:24 am
I found two possible tables, but the data there is mostly hex and non-readable. I'll take your profiler suggestion and see if I can figure it out. But somehow I doubt what I want to do is possible.
I was just hoping someone would prove me wrong. @=)
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply