Upgrade from CMS 6R2 to EPiServer 7 CMS and from EPiServer Community 4.1 to EPiServer Community 7

There is a requirement before upgrading a Community site with separate databases (CMS6r2 and Community 4.1) to EPiServer 7 and Community 7 is to merge the Community database with the CMS database. This is an instruction of how to accomplish this in MS SQL Server 2008 R2.

1. Startup
In the SSMS, right-click the Community database that shall be merged with the CMS database and generate a script.
2. Choose Objects
Select  “Select specific database objects” and then select Tables, Views, Stored Procedures and User-Defined Functions but not all objects within those boxes.  Objects to choose:

Tables
tblEPiServerCommon*
tblEPiServerCommunity*

Views
vwEPiServerCommon*
vwEPiServerCommunity*

Stored Procedures
spEPiServerCommon*
spEPiServerCommunity*

User-Defined Functions
fnEPiServerCommon*
fnEPiServerCommunity*

3. Set Scripting Options
Save the script to a specific location and save to a single file. Then press the “Advanced button”.
4. Advanced Scripting Options
General: Set “Types of data to script” to “Schema and data”.
Table/View Options: Set all to “True”.

5. Summary
Review your settings.


6. Save or Publish Scripts
The report is shown.


7. Execute the script file on the CMS database
Execute the script file that is generated (e.g. script.sql) on the CMS database.  Open the file in the SSMS. In the beginning of the file set USE [yourCMSDatabaseName] and then execute the script. Review your CMS database and verify that the objects have been transferred.


8. Configuration
In connectionStrings.config, change the connection string for the Mail database to use the CMS database. Test the site and verify that it runs correctly.

9. Upgrade
Upgrade from CMS 6R2 to EPiServer 7 CMS and from EPiServer Community 4.1 to EPiServer Community 7.

Information can be obtained from EPiServer Support.








Comments

Post a Comment

Popular posts from this blog

EPiServer CMS 11 Useful SQL Queries - 1

Here is a set of few queries that we have been using in different investigations Check How Big is your Database Get Data for Each Property and from Each Content Type Complete Tree Structure of your web site Check EPiServer DB Version Check How Big is Database SELECT      t.NAME AS TableName,     s.Name AS SchemaName,     p.rows AS RowCounts,     SUM(a.total_pages) * 8 AS TotalSpaceKB,      CAST(ROUND(((SUM(a.total_pages) * 8) / 1024.00), 2) AS NUMERIC(36, 2)) AS TotalSpaceMB,     SUM(a.used_pages) * 8 AS UsedSpaceKB,      CAST(ROUND(((SUM(a.used_pages) * 8) / 1024.00), 2) AS NUMERIC(36, 2)) AS UsedSpaceMB,      (SUM(a.total_pages) - SUM(a.used_pages)) * 8 AS UnusedSpaceKB,     CAST(ROUND(((SUM(a.total_pages) - SUM(a.used_pages)) * 8) / 1024.00, 2) AS NUMERIC(36, 2)) AS UnusedSpaceMB FROM      sys.tables t INNER JOIN       ...
Read more

EPiServer CMS 11 Useful SQL Queries - 2

Here is a set of few queries that we have been using in different investigations Get usages of EPiServer contents including pages and blocks Check Table size No contents have been added for following content types Looking into Activity Logs Unmapped Property List Get usages of EPiServer contents including pages and blocks SELECT   tct.Name,    tct.ModelType,    COUNT(tc.pkID) AS PageCount FROM   tblContent AS tc RIGHT OUTER JOIN   tblContentType AS tct ON tc.fkContentTypeID = tct.pkID Where tct.ModelType is not null and tct.ModelType not like 'EPiServer.%' GROUP BY   tct.Name, tct.ModelType ORDER BY  PageCount desc Check table size EXEC sp_spaceused 'tblBigTable' No contents have been added for following content types SELECT   tct.Name,    tct.ModelType FROM   tblContent AS tc RIGHT OUTER JOIN   tblContentType AS tct ON tc.fkContentTypeID = tct.pkID Where tct.ModelType is not null a...
Read more

Strongly Type Models in EPiServer Commerce

We can create Strongly typed models just by inheriting a proper type from EPiServer.Commerce.Catalog.ContentTypes and and decorating it with the ContentTypeAttribute attribute. that means those types will be available as ContentData. To create models for commerce content following types are available. VariationContent : A type for variation/SKU models. ProductContent : A type for product models. BundleContent : A type for bundle models. PackageContent : A type for package models. DynamicPackageContent : A type for dynamic package models. NodeContent : A type for category/node models. Examples: using EPiServer.Commerce.Catalog.ContentTypes; using EPiServer.Commerce.Catalog.DataAnnotations; namespace EPiServer.Commerce.XYZ.Models.MetaDataClasses {     [CatalogContentType(GUID = "BE40A3E0-49BC-48DD-9C1D-819C2661C9BC" , MetaClassName = "Fashion_Item_Class" )]     public class FashionItemContent : VariationContent ...
Read more