Mario Narbonne
Member
Hi,
I do have a question related to Cursor on SQL 2005. Last night, all the job were at a status of "P" (Processing) but the CPUs were all "sleeping". After investigating, I found out there was a SQL Process (Started by one of the JDE job) that was "hung" on an open cursor. In the job log (on JDE) there was a lot of messages talking about a SQL Connection failure. The cursor was on the F0002 table. After I "killed" this SQL process, all the other jobs (there were 13) continue to process and finished successfully.
I looked on the SQL 2005 side, on the databse, there is a setting called "Close Cursor on Commit Enable". On all the database, this setting is set to "False". To avoid that kind of issue, should I set this setting to "True" ? What value you guys have for your SQL 2005 databases ?
Thank you for your time.
I do have a question related to Cursor on SQL 2005. Last night, all the job were at a status of "P" (Processing) but the CPUs were all "sleeping". After investigating, I found out there was a SQL Process (Started by one of the JDE job) that was "hung" on an open cursor. In the job log (on JDE) there was a lot of messages talking about a SQL Connection failure. The cursor was on the F0002 table. After I "killed" this SQL process, all the other jobs (there were 13) continue to process and finished successfully.
I looked on the SQL 2005 side, on the databse, there is a setting called "Close Cursor on Commit Enable". On all the database, this setting is set to "False". To avoid that kind of issue, should I set this setting to "True" ? What value you guys have for your SQL 2005 databases ?
Thank you for your time.