Support CLR Stored Procedures
Is SQL azure will support Clr stored procedure, as Sql is suppurating from 2005, we invested alot in this great technology and we can't see our company migrate to azur without this feature.
A way for an SQL statement (in a procedure or trigger) to post a message to the a service bus message queue or topic.
I would have achieved this in the past with a clr trigger i guess.
My reason for this requirement would be a trigger or stored procedure would see "an event happening" - a print request going into a table or a trigger detecting something has changed requiring a user alert to be fired..
It would save the mvc controller having to call an additional command after every update etc to push a message to the queue.
I know Extended Stored Procedures are yesterdays news, but there are things for which they are very useful.
Because CLR support is not yet planned I suggest to add few public CLR methods to MASTER database like RegExSearch, RegExReplace etc. Full list of these methods (t-sql CLR functions) should be of course discussed bellow. Hope this suggestion is reasonable ;)
Thanks for your feedback. We now have the next generation of Azure SQL DB in public preview in the US and GA in Europe.
Specifically it supports CLR.
Details here http://azure.microsoft.com/blog/2014/12/11/preview-available-for-next-generation-of-azure-sql-database/ and https://msdn.microsoft.com/library/ms189524.aspx
Jay Kidd commented
If the new Azure CLR feature only supports safe assemblies, does that mean any CLR aggregates that require Format.UserDefined (e.g. binary serializers) for purposes like VerticalConcatDistinct will not be supported? :o
Long waiting CLR feature is coming, but only support safe assemblies, so disappointed
David Bowler commented
Awesome news!! Terry's child will be so proud! We can now look at migrating.
Great news! Thanks for the update. This means we can revisit the migration to Azure again this year.
I use CLR for our own aggregate functions like concatenate() and concatenatedistinct(), as well as Regex functions and Levenstein distance.
Without CLR we would have to rewrite a lot of our code. It's like going back to SQL 2000.
So we are not porting our solution until we have CLR.
To prove how important this is, we've just christened our child "CLR"
Kevin Christensen commented
We cannot consider Azure Sql until CLR is supported.
Jimi J commented
CLR Triggers and SPs are very critical for the overall performance of our application. Hence, we can't move to SQL azure.
Jay Kidd commented
Appreciate the update, we're watching for its release closely... :)
CLR is the only reason for us at this point to stick to on-premises. I wish Microsoft would consider adding CLR to Azure.
Mike Hebert commented
Not just regex - I also use it for converting datetimes between different timezones.
Henri Koppen commented
I understand the CLR is complex in a multi-tenant environment, and with worker roles it's fairly easy to work around, but I use CLR a lot (template replacements, regex) so i'd love to have it!
The only way to get real regex functionality. In fact why don't you just add in one module as a clr that has a regex match function since that's the main reason most people that I talk with use it.
Seems noone from SQL Azure want to talk about the adding back of CLR, maybe they have big issue to do that, and they haven't figured it out how to do it.
We can not migrate to SQL Azure without CLR support.
Brian White commented
Really sad to see it isn't supported. I just came across a situation perfectly solved by CLR and I was hoping to use SQL Azure as my data back end, this is a dissapointment.
SqlCacheDependency requires this.
I hope MS will add full CLR support.
We need CLR for Regular Expression parsing. If there will be no CLR in Azure, we need something TSQL-native. Regular Expressions are not new technology...
Jan Vilimek commented
Or at least allow us to create "safe" functions such as for regular expressions etc.