Re: Replacing VS .NET's SQL Server Express Edition Integration
- From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng[MSFT])
- Date: Fri, 30 Nov 2007 02:50:35 GMT
Thanks for your reply Scott,
As you said you already have an existing database that contains the
username/password, is that database previously used by membership
provider(in SQL Express)? If so, since that database has the correct
membership structure, you can surely use it. An easy way is to simply
attach the old database to new server instance(or use SSIS is they're of
diffferent version). If the database is not a membership database(but
your own user account database), I'm afraid you will need to maually import
those user account info into ASP.NET membership database through
membership APIS(such as adduser...).
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Reply-To: "Scott M." <smar@xxxxxxxxxxxxx>was
From: "Scott M." <smar@xxxxxxxxxxxxx>
Subject: Re: Replacing VS .NET's SQL Server Express Edition Integration
Date: Thu, 29 Nov 2007 21:19:14 -0500
Ok, ScottGu's blog was a good link to answer my question.
So, now I have a follow up question, which came up in Scott's blog, but
not answered:use
If I have an existing database with my own user/password data already in a
table, how can I configure ASP .NET to use that data? How would the
provider know to use my tables and what field represents what data?
"Steven Cheng[MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:n7jURomMIHA.6908@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Scott,
As for configuring ASP.NET 2.0 membership to connect SQL Server 2000, you
need to do the following things:
** use aspnet_regsql.exe tool to setup a database in sqlserver 2000 db
** add a new membership provider in your ASP.NET 2.0 application which
http://www.vikramlakhotia.com/Using_ASPNET_20_Membership_API_with_SQL_Servera connectionstring pointed to your SQL Server 2000 database
Here are two web articles provided detailed steps:
#Configuring ASP.NET 2.0 Application Services to use SQL Server 2000 or
SQL
Server 2005
http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx
#Using ASP.NET 2.0 Membership API with SQL Server 2000
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif_2000.aspx
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
issuesications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent
followwhere an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each
SQLup response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
Reply-To: "Scott M." <smar@xxxxxxxxxxxxx>Server
From: "Scott M." <smar@xxxxxxxxxxxxx>
Subject: Replacing VS .NET's SQL Server Express Edition Integration
Date: Thu, 29 Nov 2007 00:15:44 -0500
I've seen many posts and ready articles discussing how changing the
membership & roles "provider" in VS .NET is easy, but have yet to see
instructions on how to do it.
If I already have SQL Server 2000 on a machine and didn't install SQL
2005 Express with my VS .NET installation, how do I set up my existing
2000 server to be the membership & roles provider for ASP .NET?
.
- Follow-Ups:
- References:
- Replacing VS .NET's SQL Server Express Edition Integration
- From: Scott M.
- RE: Replacing VS .NET's SQL Server Express Edition Integration
- From: Steven Cheng[MSFT]
- Re: Replacing VS .NET's SQL Server Express Edition Integration
- From: Scott M.
- Replacing VS .NET's SQL Server Express Edition Integration
- Prev by Date: Re: Replacing VS .NET's SQL Server Express Edition Integration
- Next by Date: Re: Attributes.Add querystring
- Previous by thread: Re: Replacing VS .NET's SQL Server Express Edition Integration
- Next by thread: Re: Replacing VS .NET's SQL Server Express Edition Integration
- Index(es):
Relevant Pages
|