Is the membership database from CS 2007 compatible with 2008?

Reply

gavstorey Posted: Fri, Jun 27 2008 7:55 AM

rated by 0 users

I have built a group of sites using CS2007.1 Pro that share membership information in one database (~15k members) and allow users to login with the same username/password on each site (a bit like a hotmail/yahoo signin with its different products).

Now we are looking at upgrading to 2008 Pro but we would like to do each site individually rather than as a whole but this will require us to share membership between CS 2007/2008 while we upgrade each of them.  A similar membership configuration is available in the CS 2008 configs but I wanted to see if:

1. Anyone has been able to do this and it works
2. Am I missing any hidden problems (users rating/points?)
3. Would I be best to push people to signup in the cs2007/2008 forms
4. Am I missing a better approach?  Such as merging the information between databases.

Any help would be appreciated.

Reply

Ken Robertson replied on Fri, Jun 27 2008 1:02 PM

rated by 0 users

Do you have all the sites running in the same DB, or are they each in their own DB but connect to a shared set of membership tables?

In CS 2008, we removed the support for virtualization, so you would likely need to separate the sites out to separate DBs.  You could basically take a backup of your current DB, restore it to multiple new DBs, then you'd mainly want to remove the SiteSettings entries for the other sites, and perhaps some of the posts just to free up some space.

In terms of the membership, CS uses the ASP.NET Membership providers, which all provided with ASP.NET.  We don't make any changes to them, so membership is always compatible.

I don't believe the sites would share ratings/points.  That is something specific to CS that would be separate for each site.  Using shared membership, it only shares the user's core profile settings such as username/password, display name, email address, timezone, birthday, location, etc.  Other settings that are CS-specific, such as their editor, whether they want email notifications, etc, are store within CS and not the Membership tables, so they are not shared.

Reply

gavstorey replied on Mon, Jun 30 2008 6:43 AM

rated by 0 users

It sounds like it will not be a problem which is a relief as I was hoping that I would not have to upgrade all of the sites/themes/custom code at the same time. 

My initial concern had been because I had seen the role/permission interface changes between CS2007/2008 and I had thought CS used a custom membership provider to disconnect CS from any ASP.net updates.

But either way I will give this a whirl and see if any issues crop up, but I am feeling more positive about it now.

Gav