May 11, 2009 at 10:36 am
Hard to know, but I'll bet it's related to the size. Based on your descriptions and the documentation, I'd guess that was it.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 11, 2009 at 10:42 am
I will talk to the developers about the way this has been coded. Doesn't look like the cursor and dynamic SQL are strictly necessary, although it is not easy to tell (I'm not familiar with the logic).
There has to be a set-based solution for what this sproc is doing, but getting there may be a challenge.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
Viewing 2 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply