Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
mark061
Starting Member
2 Posts |
Posted - 2010-11-18 : 16:25:15
|
We're currently trying to upgrade from version 7.7 to version 8.1 of Siebel (running on MSSQL2005). There is a particular query that is causing problems at the moment. When run directly against the database it returns instantly ('0 seconds') but from the application it seems to hang on fetching the data from the cursor. This is the sort of thing we're seeing in the application logs (note the 21 second delay):10:11:39 Begin: Fetch for Sql Cursor at 18c64d0810:12:00 Begin: Close Sql Cursor at 18c64d08I'll admit to not knowing too much about cursors as we don't use them in our homegrown code. The usual tricks of looking at the QEP, missing indices reports, tuning the statement etc are not producing anything helpful. I don't really expect them to seeing as the sql runs well taken out of the application. The problem definitely seems to be inside the cursor but we're at a loss as to why this should take so long. Any suggestions or pointers would be very welcome.thanksMark |
|
madhivanan
Premature Yak Congratulator
22864 Posts |
Posted - 2010-11-19 : 03:13:41
|
Can you post the queries that you used?MadhivananFailing to plan is Planning to fail |
 |
|
mark061
Starting Member
2 Posts |
Posted - 2010-11-19 : 07:03:36
|
MadhivananI'd just got as far as collecting some trace data (which showed 31M rows being read instead of a couple) when the developer arrived and said they'd found where the vendor's code differed between releases. They've pasted the old version of the code into the application and everything works fine now. Progress eh?Thanks for your offer of help.Mark |
 |
|
madhivanan
Premature Yak Congratulator
22864 Posts |
Posted - 2010-11-19 : 07:49:35
|
Ok. No problemMadhivananFailing to plan is Planning to fail |
 |
|
|
|
|