Thanks for the suggestion. We've been using Profiler for this all day to
watch the connections and it doesn't appear to be creating new ones. Is
there any way SQL Server could be grabbing a connection to do some
transactional commits or logging work on a large update or insert even after
the scri
I haven't peeked at the code, but based on your description, I'll bet that it's
closing and reopening connections for each SQL string instead of using
connection pooling, etc.
Fire up SQL Profiler and cap a trace of connection events during the
installation and that will tell you for sure what
2 matches
Mail list logo
