Article ID: 2006191 - View products that this article applies to.
This article provides information about two specific limitations when using ASP.net in conjunction with a Microsoft SQL Azure database.
Issue 1 - Problems with the aspnet_regsql tool:
The aspnet_regsql.exe tool will fail to run against a SQL Azure database. When trying to create a database with the aspnet_regsql.exe tool, the user will encounter one of the following errors:
-- or –
Issue 2 - Asp.Net Session State Management:
A user’s session will not expire if the ASP.net web application uses a SQL Azure database for session state management.
Cause 1 - Microsoft SQL Azure is a cloud-based relational database platform built on SQL Server technologies. The aspnet_regql.exe tool works with the .sql scripts which are located in the .Net framework directory, however SQL Azure databases do not support some of the SQL statements used in these raw .sql scripts.
Cause 2 -Asp.Net session expiration functionality is implemented through stored procedures that are scheduled through jobs in SQL Server. SQL Agent manages these jobs. However, SQL Azure databases do not support SQL Agent.
To configure SQL Azure databases for Asp.Net membership, role manager, profiles, personalization, and SQL Web event provide features, please do the following:
Note: You may receive the following message while executing the scripts: "Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information schema, sys, or yourself." This message can be ignored.
The workarounds provided here do not work for ASP.Net SQL Session State Management features. Microsoft does not support SQL Session State Management using SQL Azure databases for ASP.net applications.
There is a modified aspnet_regAzure.exe tool that is available for use. You can download this tool from here. This tool only supports configuring a SQL Azure database for certain Asp.net features. This tool does not support all the functionalities of aspnet_regsql.exe, and it is not supported by Microsoft.
You can find more documentation on Guidelines and Limitations for SQL Azure databases here.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.