I have a simple DBI do that is running a stored procedure on sql server. The stored procedure may return informational messages and throw various low priority errors during execution. Running the stored procedure from sql server managements studio executes perfectly fine, and I see the informational messages as intended. However, running this from my perl script terminates prematurely. I seem to be able to link it to DBI possibly automatically terminating the connection as soon as it receives the first select/response. Any idea how I can tell DBI to wait until the stored procedure actually completes before disconnecting?