May 10, 2012 at 12:34 am
I use a dot.net application to do some import and arranging of data. there for I use some stored procedures which contains cursors; even nested cursors. Calling the stored procedures from the application will take about 5 minutes to execute and finish the work.
Calling the same stored procedure from within the Management Studio will take up to 40 minutes to execute and finisch.
It's the same proecdure and the result is the same. Why the difference?
Also, is het better to call a stored procedure from a dot.net application or is it quicker to use plain sql statements in het application? Using stored procedures maker it easier to handle and maintain for me. But is it realy better (in performance)?
thanx for the time
May 10, 2012 at 8:17 am
Hands down your best approach is to get rid of the cursors all together. Then you don't have to worry as much about performance issues like you are having. Are you talking millions of rows? If not, then 5 minutes to do some data massaging is WAY too long.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply