Upgrade and morpheus

rated by 0 users
Answered (Verified) This post has 2 verified answers | 11 Replies | 6 Followers

Top 100 Contributor
222 Posts
Points 3,455
Edoardo posted on Wed, Feb 6 2008 5:40 PM

Folks,

My site leverages an aspnetdb dataset that is hosted in a separate database from the CS database in order to share it with other applications.
This is done redirecting the database connection string in the web.config files as per morpheus workings.

Is the upgrade program aware of a morpheus-enabled deployment? Will it work fine?

Thank you!

Bye.
Dodo.

Running CS 2008.5 (v4.1.30912.2823) on Windows Server 2008 RTM and SQL2005 w/SP2.

Answered (Verified) Verified Answers

Top 25 Contributor
1,878 Posts
Points 37,860
CS Developers

Hi Edoardo,

Since the remote data is in an aspnetdb and we *never* touch that schema, you shouldn't have any issues. That said, I would strongly recommend that you backup your database and site before attempting to upgrade.

Thanks...

One is glad to be of service...

Jose Lema

  • | Post Points: 35
Top 25 Contributor
1,878 Posts
Points 37,860
CS Developers

Howdy,

Yes. As we announced just prior to the CSDC, we have decided to remove the virtualization feature from Community Server. In the UpgradeNotes.txt file, we mention this exact scenario...just as you mention it. So, if you had 3 sites in a single database, you should make three backups and run the upgrade tool three times, once against each database selecting a different site to upgrade each time. The upgrade tool does the removal of all "other" sites data as part of its process.

Hope that helps...

One is glad to be of service...

Jose Lema

  • | Post Points: 35

All Replies

Top 25 Contributor
1,878 Posts
Points 37,860
CS Developers

Hi Edoardo,

Since the remote data is in an aspnetdb and we *never* touch that schema, you shouldn't have any issues. That said, I would strongly recommend that you backup your database and site before attempting to upgrade.

Thanks...

One is glad to be of service...

Jose Lema

  • | Post Points: 35
Not Ranked
12 Posts
Points 195
We have many community server instances running on the same database. Do we need to separate all now? In case that the answer is yes, do you have a tool to clean up everything? I think that we should replicate all the databases for all the different implementations, and then run a clean up on each one to only keep the data that we need
Top 25 Contributor
1,878 Posts
Points 37,860
CS Developers

Howdy,

Yes. As we announced just prior to the CSDC, we have decided to remove the virtualization feature from Community Server. In the UpgradeNotes.txt file, we mention this exact scenario...just as you mention it. So, if you had 3 sites in a single database, you should make three backups and run the upgrade tool three times, once against each database selecting a different site to upgrade each time. The upgrade tool does the removal of all "other" sites data as part of its process.

Hope that helps...

One is glad to be of service...

Jose Lema

  • | Post Points: 35
Top 25 Contributor
856 Posts
Points 13,265

I was wondering if you had gotten the "splitter" working.  Lucky that I stumbled on this thread.  BTW, there seems to be something funky with the text editor.  When I first come into the page, I can't get the cursor in this text area.  I had to click on one of the buttons first and then it allowed me to type.

Take it easy,
Bill 

  • | Post Points: 20
Top 10 Contributor
3,399 Posts
Points 65,060
CS Developers

Bill Bosacker:
BTW, there seems to be something funky with the text editor.  When I first come into the page, I can't get the cursor in this text area.
 

TinyMCE 3.0 appears to only allow clicking the first "row" with the cursor in IE (possibly only 7).  I've not seen this behavior in other browsers.

Ben Tiedt's Blog

  • | Post Points: 5
Top 10 Contributor
3,399 Posts
Points 65,060
CS Developers

Ben Tiedt:
TinyMCE 3.0 appears to only allow clicking the first "row" with the cursor in IE (possibly only 7).
 

This issue has been resolved and will be included in the next update to cs.org and the next release of CS2008.

Ben Tiedt's Blog

  • | Post Points: 20
Top 25 Contributor
856 Posts
Points 13,265

Very cool.  I was going to try upgrading my sites to the beta this weekend, but I think I'll wait till the next release. Smile

  • | Post Points: 5
Top 100 Contributor
222 Posts
Points 3,455
Edoardo replied on Tue, May 13 2008 5:55 AM

Well, actually I did have issues.

During the upgrade from CS 2007 to 2008 one of the Schema Patches adds the MediaManager role and the associated permissions on CS tables point is that the aspnet_roles table that is referenced is the one on the local CS database. This caused my first attempt to upgrade to fail.

I tweaked the upgrade sql scripts searching and replacing all aspnet_ occurencies with myaspnetdbdatabase.dbo.aspnet_  and removed square brackets were applicable. This worked fine for me.

Has the number of sprocs to copy in the custom aspnetdb changed? The usual 11 sprocs?

Thank you.

Bye.
Dodo.

Running CS 2008.5 (v4.1.30912.2823) on Windows Server 2008 RTM and SQL2005 w/SP2.

  • | Post Points: 20
Top 25 Contributor
1,878 Posts
Points 37,860
CS Developers
Jose Lema replied on Wed, May 21 2008 4:38 PM

Hi Edoardo,

No, no new sprocs have been added. It's still the same 11.

One is glad to be of service...

Jose Lema

  • | Post Points: 5
Not Ranked
1 Posts
Points 20
Scoot replied on Wed, Jul 9 2008 9:42 AM

Hello,

The upgrade process of removing virtualization is failing for us. We have many instances. The upgrade process runs for several hours, then dies after removing 20 sites or so. Funny thing is, I still see all the sites it said it removed ion the cs_sites table.

There must be a sql script around which the upgrader tool uses to remove the sites. How can I get it?

 

Scott

  • | Post Points: 20
Top 25 Contributor
856 Posts
Points 13,265

Hey Scott,

The most common reason for failing that I have come across is due to foreign keys that the upgrader is not aware of.  To fix the issue, use SQL Server Management Studio to create a script of your database schema that includes drops.  After you have the script, just run the portion that drops the foreign keys.  They should all be together in one section.  Then backup your database and try it again.  You might run into more issues after that, but at least that is one item off the list.

Once you have everything converted, create a brand new installation of CS 2008 and create a script for that new database.  This time you want to look for the creation of the foreign keys and just run that section on your converted database.  Make sure that the script tests for the existence of a foreign key as some foreign keys will be added back by the upgrader.

Take it easy,
Bill

  • | Post Points: 5
Page 1 of 1 (12 items) | RSS
Powered by Community Server (Commercial Edition), by Telligent Systems

Copyright© 2008 Telligent Systems Inc. All rights reserved
CommunityServer.com  •  Telligent.com