I have been running some scheduled batch jobs for a period of time on sone large files overnight.
I have a SQL job that updates a table with about 700,000 rows.
This has been running fine till recently, where I am getting the error 0xE0434352 which stops the job on CommandTimeout line.
Thinking that this was due to the increase in the size of the database I have increased the timeout size to from 1 to 2 to 3 hours Command2a.CommandTimeout = 10800.
However this still fails each night on the server.
The next day on finding the issue I run the job manually and all closes fine, within 1 hour and no errors.
I am using SQLserver 2008 R2
Any suggestions as to the issue