Using SQL Server 2008 for an ASP.NET 2.0 Provider

Question

I tried to configure SQL tables for the ASP.net 2.0 membership provider by clicking ASP.net Configuration in Project.

I completely uninstalled SQL 2005 Express and installed SQL 2008 Express instead.

It seems that it cannot connect to the database.

Does anyone know how to get this hotfix to use 2008 instead?

Answer 1

Try setting up the database entry "aspnet_regsql" on the VS command line.

Then configure the database and finally change the connection string in the web.config file.

ASP.NET SQL Server Registration Tool (Aspnet_regsql.exe)

Answer 2

How is an instance of a SQL 2008 installation called? What does your connection string look like for a membership provider?

As far as I know, there is (or was) a failure in installing SQL Server 2008 Express, even if you decide to install it as a default instance, it will still make it a "named instance" called ". \ SQLExpress" instead. Could this be a problem?

Mark

Answer 3

As Mark already pointed out, this could be a problem with the instance name. This is fixed in SQL Server 2008 Express Service Pack 1. For more information and a workaround, see this Microsoft KB article .

Answer 4

SQL 2005 and 2008 are configured by default in a fixed latency state - and this means that SQL will not access the database except through shared memory, even with integrated security.

You need to enable TCP / IP or named pipes for client protocols for the server (since ASP.NET is negotiating with SQL if you have not configured DSN to use shared memory.

I can’t remember the exact steps in 2k8, since I needed to do this once, but in 2k5 you had to open SQL Server configuration manager, select your own client configuration, client protocols and enable TCP / IP and Named Pipes - this is a similar process for 2k8, as I recall.

Answer 5

The ConnectionStringName used in the membership tag must be changed to the current connection string in which the membership tables were created.

If connectionStringName does not indicate a valid connection string name in the connectionStrings tag, membership tables cannot be used by the application.