Jan 26, 2014 at 11:33 AM
Edited Jan 26, 2014 at 1:32 PM
i just created a new be blog on Azure Websites. This version seems not to be azure website / sql ready.
Http compression is enabled by default in be settings. Now the content gets double compressed (be and azure iis) und you can't access the site.
Workaround: Update settings in azure sql:
SET SettingValue = 'False'
WHERE SettingName = 'enablehttpcompression'
The compression is disabled by default in xml settings. So the problem occurs only if you use azure sql.
Error on adding data to azure tables:
Tables without a clustered index are not supported in this version of SQL Server. Please create a clustered index and try again.
Workaround: not yet discovered :)
It would be great if someone has a solution for this problem. Additionally it would be nice to test be on azure websites / sql azure before releasing new versions. Otherwise note that be is not fully tested on azure and remove be from the azure website catalog.
Jan 26, 2014 at 5:00 PM
The workaround is change to clustered index:
drop INDEX [idx_be_CustomType_ObjectId_BlogId_Key] ON [dbo].[be_CustomFields]
CREATE UNIQUE CLUSTERED INDEX [idx_be_CustomType_ObjectId_BlogId_Key] ON [dbo].[be_CustomFields]
Pulling app for not supporting feature it never claimed to support in the first place would be odd :)