At this second I can not delve into the DBI code itself, but I believe there is a MSSQL option to set the timeout of a client connection.

What is happening, by the sounds of it, is the DBI is dropping the connection, your program sees the drop and continues. Your line in the eval: $dbh->commit; will commit the code even if it completely screwed up. Your not checking to see if it was a success before commiting.

In SYBASE you can extend the time out using the dbi:Sybase:timeout=240 connector. In MYSQL you can use the mysql_connect_timeout=240 in the connector like sybase.
I do not see this option in MSSQL, but my knowledge there is lacking a bit.

Hope this helps, and isn't a complete waste of space.
--