November 5, 2010 at 8:32 am
I've been testing CLR Vs T-SQL versions of linear regression aggregates in SQL2008.
The gist is that CLR is slightly slower if I aggregate an entire table however when I introduce a GROUP BY statement the execution plan shows that the entire set is sorted prior to aggregation so the CLR:T-SQL Cost ratio for the Aggregate goes from being 49:51 to 89:11
Has anyone come across this problem and if so how did you solve it?
February 15, 2016 at 10:05 am
Hi David,
Many years later... I'm interested in iteratively using regressions over up to 1000 lines within a table that contains millions lines. I'm wondering if you achieved to explain why SQL uses the SORT? Also, were you able to achieve better performance with your CLR-aggregate function?
Thank you !
April 30, 2016 at 2:53 pm
Just FYI, there is an oddly similar thread on the MSDN forums ;-):
It does not seem as though there is a fix as I tested with SQL Server 2014 and the same error occurs when attempting OPTION (HASH GROUP).
SQL# — https://SQLsharp.com/ ( SQLCLR library ofover 340 Functions and Procedures)
Sql Quantum Lift — https://SqlQuantumLift.com/ ( company )
Sql Quantum Leap — https://SqlQuantumLeap.com/ ( blog )
Info sites — Collations • Module Signing • SQLCLR
February 15, 2019 at 8:03 am
Now that Microsoft Connect has been moved over to UserVoice, the new URL for the request to fix this is:
Please support that request by voting for it. Thanks!
Take care, Solomon..
SQL# — https://SQLsharp.com/ ( SQLCLR library ofover 340 Functions and Procedures)
Sql Quantum Lift — https://SqlQuantumLift.com/ ( company )
Sql Quantum Leap — https://SqlQuantumLeap.com/ ( blog )
Info sites — Collations • Module Signing • SQLCLR
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy