Good to know, thanks for the quick reply.

Regards,

Scott

Your ideas are much appreciated!

Actually I may be able to get around this by passing the connection metadata into a separate parent package variable. The dtexec arg string is...

Fair enough, but the beauty of it is the package gets everything it needs in one manner, from the parent variables. I used to get some of the metadata from...

Interesting, would work fine but I want to keep these as stand alone as possible. I think that solution might make unit testing and running these individually on the fly...

Thanks very much for the replies, at the very least the usage of the column is clear.

Seems to be it would be more useful if the user_lookup values were...

Thanks for your reply. I'm still a bit confused can I rephrase my question here?

This confusion started with this script I got off the net (maybe here) for analyzing indexes,...

Thanks so much for all the suggestions. If I find anything out I'll post back.

True, I like that idea.

The only catch is I've already standardized and coded the logging procs, and interspersed them in the code. I was hoping there was something easy where...

I'm referring to the capability of using one server as a master to execute jobs on target servers.

There's SSIS tasks that can copy jobs, but I'm not sure how it'll...

True. We have enough office automation related issues.

I took a look and the SSIS packages are just converting the xls files to csv. This can be done without automation -...

I can tell by the columns its our code. Probably a proc that's stuffing more data than it needs to in a table variable and processing it. I know there's...

Its using automation. Resources are definitely a concern. Just not sure how much I should be.

bummer that what i was afraid of. thanks for your help.

--

Scott

We did this some time back. It went very well. There was only one query that broke, and it was obvious. I don't remember the details, something about the ORDER...

To get the running traces:

SELECT

*

FROM

fn_trace_getinfo(default)

WHERE

property = 5 and value = 1

There's a tutorial here on how to analyze the default trace:

http://www.sqlservercentral.com/articles/SQL+Server+2005/64547/

It may be a good...