Remove serialization during CLR aggregate calculation - by Anton Plotnikov

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 778558 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 2/5/2013 4:44:18 AM
Access Restriction Public

Description

My CLR aggregate produces a lot of intermediate results. Consequently, serialization/deserialization of aggregate during each row processing leads to great perfomance issues. It is possible to eliminate excessive serialization and improve perfomance?
Sign in to post a comment.
Posted by Anton Plotnikov on 8/19/2013 at 5:48 AM
Hello.

It is a vary sad that SQL Server's team can't remove obvious performance issue from product costs a lot of thousands $.

--
Anton
Posted by Microsoft on 2/27/2013 at 12:38 PM
Hello Anton,
Thanks for your feedback. I am closing this as "won't fix" given the other high priority requests in our pipeline. Even if we close the item, it remains in our bug database so we can look at it in the future when our business priorities change.

--
Umachandar, SQL Programmability Team