Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SqlAzure does not support sys.sp_addextendedproperty #513

Closed
colinangusmackay opened this issue Jul 28, 2014 · 7 comments
Closed

SqlAzure does not support sys.sp_addextendedproperty #513

colinangusmackay opened this issue Jul 28, 2014 · 7 comments

Comments

@colinangusmackay
Copy link

A SQL Azure database does not support a number of things that are available in SQL Server 2012, such as sys.sp_addextendedproperty which means that WithColumnDescription() fails when applied to a SQL Azure database, although it works perfectly fine when applied to a SQL Server 2012 database.

@tommarien
Copy link
Contributor

@colinangusmackay You are right and there seems to be no way around this limitation, either we have to create a special processor that throws an error on this situation or we leave it as is

@eldersantos
Copy link

What about create a new Generator called SQL Azure. I have been working with SQl Azure and there is a lot of diffs between SQL Server on premisse and SQL Azure

@tommarien
Copy link
Contributor

@eldersantos Just the description feature seems like not enough to warrant for a new processor/generator any other differences that may have an impact ?

@eldersantos
Copy link

@tommarien there are severals, but thinking only about DDL instructions I can say a clustered index is always required on all SQL Azure tables. SQL Azure does not support heap tables, the create table statement will not fail but the INSERT operations will until a clustered index is created.
Sql Azure even supports some of the more specialized data types such as the spatial data types geography and geometry, hierarchyid, but maybe these is too specific.

@tommarien
Copy link
Contributor

@eldersantos Those types are not specific to SqlAzure, heap tables is correct but not sure how to put that in a specific provider/generator though

@eldersantos
Copy link

@tommarien I think it is not enough to a new generator too.
Onde option is always consider a PK with clustered index in a table for sql server generator or at least show a warning when the developer do not create one.

@tommarien
Copy link
Contributor

I'll close this issue because not enough reasons to create a sqlazure provider atm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants