Allow OPTION(HASH GROUP) with SQLCLR UDAs

Currently, it appears that when SQLCLR UDA are used with a GROUP BY clause, a StreamAggregate operation must always be used. Attempting to specify OPTION(HASH GROUP) on a query like this:

Declined

SQL OSSuggestions

Company Response

Microsoft

Company Response

Up: 24<=-=Jan 4 2011 4:40PM=-=>Hi Bob,Thanks for the feedback. We�ll consider fixing this in a future release. Can you tell me more about the scenario? What UDAgg were you implementing and why? Feel free to contact me by email if you want.Best regards,Eric HansonProgram Manager, SQL Server Query Processing(email removed)<=-=Jan 4 2011 5:15PM=-=>Sure Eric, there are a few that I can think of. This actually came about because of the following forum question:http://social.technet.microsoft.com/Forums/en-US/sqlnetfx/thread/957a5b94-c7d0-49d8-928d-7cccff14b0c6. I realized that the sort was required because of choice of stream aggregate. And he can�t put on every index possible to get rid of the sort.Second is that the spatial aggregates in Denali would need this funtionality. Related to that is that there�s a vendor product that consists of a library of UDAs, Fuzzy Logix (http://www.fuzzyl.com/in-database_analytics.php#) that could benefit from this flexibility as well.Hope this helps,Cheers, and thanks,Bob<=-=Apr 5 2011 8:07AM=-=>I can confirm that this is happening to us as well. We needed a custom aggregate function, and we were very surprise to find out that there was an unnecessary sort happening that was hogging the query. It�s very unfortunate that the OPTION doesn�t work. Please fix that.

0 Comments

You must to comment