Security :: Membership Against Multiple Database?

I am facing a very unique situation and need help. My problem is as follows:1. I have a basic ASP.NET website (3.5 is it helps on IIS 7) where I have implemented Membership for Authentication.2. The site caters to multiple companies (Say Company A, Company B etc.).3. For each company I need to have different database (SQL 2008). This is mandatory as i can use multiple Application in there.Now as far as the flow is concern its pretty simple:1. The user comes to this site with a QueryString like cid=123 (in actual there is a HttpModule for this, cid=123 is just for this forum purpose).2. The site using the cid=123 gets to know this user is for Company A (i have a WCF service for this, how it works is not a problem.), along with that I also get the connectionstring for the database this user should use.3. For Business implementation i have handled this nicely in my DAL Layer.4. The problem comes with Membership.5. In Membership I have writtent a custom provider, that assigns the connection on teh fly.6. But this happens only once for the application. i.e. the connectio string gets cached at application level.7. The connection string does not change untill I reset my IISwhere i can have a single WebSite, catering to different companies, using seperated databases and using Membership for Authorization.

public class CustomMembershipProvider : SqlMembershipProvider
{
public override void Initialize(string name, System.Collections.Specialized.NameValueCollection config)

[code]...