5

I have created user defined data types in my project. Now I am going to deploy my project on Windwos Azure.

I have defined user defined CLR data types in my sql server 2008 database. As much as I have read about user-defined CLR data types, these are not supported in Windows Azure SQL Database.

Is there any alternative for databases with user-defined CLR datatypes when migrating to Windows Azure SQL Database?

7
  • Are you porting your SQL Server 2008 database to a Windows Azure SQL database?
    – STLDev
    Commented Jun 11, 2013 at 11:15
  • 2
    User-defined CLR datatypes are what are not supported in a Windows Azure SQL database. Is your user-defined type a CLR type?
    – STLDev
    Commented Jun 11, 2013 at 11:17
  • Yes these are CLR types Commented Jun 11, 2013 at 11:18
  • 2
    Ah - then you do have a problem on your hands. As far as I know, there is currently no way to do what you need to do.
    – STLDev
    Commented Jun 11, 2013 at 11:21
  • 1
    If you require this flexibility - you could always use an Azure VM to host SQL Server (IaaS). You would have to manage the OS and DB software updates yourself though. Azure SQL Server VMs can scale and support high availability - it's just a lot more work (and probably cost) if you require it. Commented Jun 11, 2013 at 11:39

2 Answers 2

4

User-defined CLR data types are not supported on Windows Azure Database. Relevant documentation:

Windows Azure SQL Database does not support user-defined common language runtime (CLR) data types.

Source: Data Types (Windows Azure SQL Database).

The following features that were new to SQL Server 2008 are not supported by Windows Azure SQL Database: (...) Extension of spatial types and methods through Common Language Runtime (CLR) The following features that were new to SQL Server 2005 are not supported by Windows Azure SQL Database: (...) Common Language Runtime (CLR) and CLR User-Defined Types

Source: SQL Server Feature Limitations (Windows Azure SQL Database).

Alternatives:

1) Change the application to use only data types supported by Windows Azure SQL Database. Downside: requires code and database changes. Upside: hosted, highly available service.

2) Use an on-premises or third-party SQL Server. Downside: you have to host SQL Server yourself or pay someone to host it; latency may be an issue; availability and management is your concern. Upside: full SQL Server compatibility.

3) Host SQL Server in Windows Azure Virtual Machines using VM images published by Microsoft. Downside: management is your concern; high availability requires additional configuration. Upside: full SQL Server compatibility; low latency; highly available infrastructure.

3

CLR is now supported on SQL Azure databases.

http://feedback.azure.com/forums/217321-sql-database/suggestions/401015-support-clr-stored-procedures

I haven't created an assembly yet, since that's the tricky part.

It's not clear if this is only for SAFE mode.

3
  • 1
    Microsoft has pulled the rug out from everyone's feet after having added that feature: brentozar.com/archive/2016/04/…
    – easuter
    Commented Apr 11, 2016 at 15:22
  • 1
    I never trusted CLR on Azure so never implemented it. Thanks for making that official. Commented Apr 11, 2016 at 18:46
  • Yeah, and with a 7 day warning period to boot. A real kick in the nuts.
    – easuter
    Commented Apr 11, 2016 at 22:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.