I get the following error when trying to install on Umbraco Azure:
Umbraco Courier Installer encountered some errors
+ umbraco.DataLayer.SqlHelperException: Umbraco Exception (DataLayer): SQL helper exception in ExecuteNonQuery ---> System.Data.SqlClient.SqlException: Keyword or statement option 'pad_index' is not supported in this version of SQL Server. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at umbraco.DataLayer.SqlHelper`1.ExecuteNonQuery(String commandText, IParameter[] parameters) --- End of inner exception stack trace --- at umbraco.DataLayer.SqlHelper`1.ExecuteNonQuery(String commandText, IParameter[] parameters) at Umbraco.Courier.UI.Usercontrols.Installer.Page_Load(Object sender, EventArgs e)
This is due to SQL Azure not supporting certain options such as padding and page locks.
The only fix is having the courier SQL script cleaned up to be compatible with SQL Azure.
For now one work around would be to migrate your database to a regular SQL server, perform the installation (having your Azure web app point to this db) and migrate back to SQL Azure afterwards.. A bit cumbersome if you're already in production though.
DB error while installing on azure
I get the following error when trying to install on Umbraco Azure:
Umbraco Courier Installer encountered some errors
umbraco.DataLayer.SqlHelperException: Umbraco Exception (DataLayer): SQL helper exception in ExecuteNonQuery ---> System.Data.SqlClient.SqlException: Keyword or statement option 'pad_index' is not supported in this version of SQL Server. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at umbraco.DataLayer.SqlHelper`1.ExecuteNonQuery(String commandText, IParameter[] parameters) --- End of inner exception stack trace --- at umbraco.DataLayer.SqlHelper`1.ExecuteNonQuery(String commandText, IParameter[] parameters) at Umbraco.Courier.UI.Usercontrols.Installer.Page_Load(Object sender, EventArgs e)
Hey Nate,
This is due to SQL Azure not supporting certain options such as padding and page locks.
The only fix is having the courier SQL script cleaned up to be compatible with SQL Azure.
For now one work around would be to migrate your database to a regular SQL server, perform the installation (having your Azure web app point to this db) and migrate back to SQL Azure afterwards.. A bit cumbersome if you're already in production though.
Grtz
L
You can get the manual install files from here:
http://umbraco.com/help-and-support/customer-area/courier-2-support-and-download
Open the zip file and in the sql folder you can find app.sql and create.sql
App.sql should run without problems, create.sql needs to be modified to fit azure sql standars.
When those 2 scripts have run, you should be able to just copy the flat files to your sites and have something running.
Consult the manual install docs to verify you do everything needed to install manually on azure
Incase anyone else is looking, you have to execute this script after you get the error during installation:
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
IF NOT EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[UCUserSettings]') AND type in (N'U'))
BEGIN
CREATE TABLE [dbo].[UCUserSettings](
[User] [nvarchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[Key] [nvarchar](250) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[Value] [nvarchar](2500) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
CONSTRAINT [PK_UCUserSettings] PRIMARY KEY CLUSTERED
(
[User] ASC,
[Key] ASC
)WITH (STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF)
)
END
GO
Thanks nate!
is working on a reply...