Comments
4 comments
-
So have you tried it by creating clusters?
-
Yes. I am using the EF (4.1) with model-first approach. the EMDX sql file creates all the clustered indexes as required.
The Azure DB that i am trying to upgrade is failing on the table that has a clustered index.
Problem is: Azure requires a clustered index which means i can't drop it (as its required)
Regards
Roy -
Hi UKRoyster
I believe that we already have a support call raised with you, call reference F0068883.
I have just updated the call and sent an e-mail to you.
Many Thanks
Eddie -
For anyone else that has the clustered index issue while upgraded to Azure using SQL Compare 10.2.6.114...
Red-gate have reported bug with reference number is SC-6147.
To get around it while bug bieng fixed, download SQL Compare V9.5
ftp://support.red-gate.com/patches/SQL_ ... 180843.zip
Add comment
Please sign in to leave a comment.
I have a local sql database thati am comparing to the SQL Azure. Script is generated but when i run it in Azure i get the following issue...
Msg 40054, Level 16, State 2, Line 1
Tables without a clustered index are not supported in this version of SQL Server. Please create a clustered index and try again.
Msg 3727, Level 16, State 0, Line 1
Could not drop constraint. See previous errors.
Is there an option to say that it must conform to SQL Azure?
Require urgent advice if possible,
Thanks
Roy