In this tutorial we will discuss an overview of SQL Server servicing installation. It is possible to upgrade any installed SQL Server 2008 component with a SQL Server 2008 servicing update. In this case, if the version of the component is later than the version update available then the Setup program will not update it.

Using Two ASP.NET Membership Providers to CreateUser VB

This tutorial shows you how to use the CreateUserWizard control with two SQL Membership Providers in an ASP.NET Web Application, and how to programmatically switch between the two. VB.NET.

In this tutorial, we will demonstrate how to use two different ASP.NET Membership Providers to utilize two separate SQL Server Databases for creating users. By Default, ASP.NET Membership provides you with powerful tools to implement a membership system into your web application.

Even with all the power and functionality we get with the Membership class, it is surprisingly easy to work with and implement, as well as customize. In this tutorial, you will learn how to utilize two SQL Membership Providers to register users for two separate databases.

To start, we will create a new Web Site in Visual Studio, and then click Website > ASP.NET Configuration. Next, select the Security tab and click either the 'Use the security Setup Wizard to configure security step by step' or the 'Select authentication type' link.
Whichever method you choose, you will want to select the Access method 'From the internet'. For this example, we will not enable Roles or create users just yet.

Once we have set the Access method, we can close the browser for the Configuration. You should now notice that Visual Studio has created a database for our Membership. Right-click the App_Data folder in Solution Explorer, then choose Refresh - you will notice a SQL Server database named ASPNETDB.MDF
Before we do anything else, let's Copy and Paste this database in Solution Explorer. Rename the copied database. Because we used ASP.NET Configuration to set-up the Membership class, by default the database being used is the ASPNETDB.MDF
Now to add our Secondary SQL Provider, we will need to edit the Web.config. First, add the connection strings for each database:

I just signed up at Server Intellect and couldn't be more pleased with my Windows Server! Check it out and see for yourself.

Inside the <system.web> tags, add the following:

Notice that our default provider is the one that ASP.NET created automatically for us. Then we basically just duplicate it.
The next step for us is to create a Register User page. The easiest way to do this is to use the CreateUserWizard ASP.NET control, which can be used with Custom Providers, as they inherit from the default class. Create a Register.aspx and drag on from the Toolbox a CreateUserWizard control. You should have something like this:

If we run this page right now, the Wizard will use the default Membership Provider to create a new user. So let's add an option to choose which provider to use; let's add a RadioButtonList:

We migrated our web sites to Server Intellect over one weekend and the setup was so smooth that we were up and running right away. They assisted us with everything we needed to do for all of our applications. With Server Intellect's help, we were able to avoid any headaches!

Notice that we have also added an OnSelectedIndexChanged event handler to the RadioButtonList, as well as set AutoPostBack to true. This is because we want to change the Provider when the option is selected. To do this, we simply add the following in the code-behind:

Now when this page is run, we can programmatically set the Membership Provider at runtime, allowing us to add users to two separate ASP.NET Membership tables. To make the process a little cleaner, we could add an AJAX UpdatePanel to mask the PostBack on selecting a Radio option:

We moved our web sites to Server Intellect and have found them to be incredibly professional. Their setup is very easy and we were up and running in no time.

The entire code-behind will look something like this: