Move the Microsoft Dynamics CRM databases to another SQL Server and SQL Server Reporting Services server in the same domain, and leave the Microsoft Dynamics CRM Server on the existing server

  1. Back up the Organization_MSCRM database and the MSCRM_Config database. To do this, follow these steps:
    1. On the computer that is running SQL Server, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
    2. Expand Databases, right-click the Organization_MSCRM database, point to Tasks, and then click Back Up.
    3. Under Destination, add the location to save the backup file, and then click OK.
    4. Repeat steps 1b and 1c for the MSCRM_Config database.

    Note If you must move more than one organization, repeat steps 1a-1d for each organization database.

  2. Restore the Organization_MSCRM database and the MSCRM_Config database on the new computer that is running SQL Server. To do this, follow these steps:
  3. On the new computer, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
    1. Right-click Databases, and then click Restore Database.
    2. Under Destination to restore, type the name of the Organization_MSCRM database in the To database box.
    3. Under Source for restore, click From device, click the ellipsis button (...), add the Organization_MSCRM database, and then click OK.
    4. Click to select the Restore check box, and then click OK.
    5. Repeat steps 2b-2e for the MSCRM_Config database.

    Note If you must move more than one organization, repeat steps 2a-2f for each organization database.

  4. Update the following registry subkeys on the computer that is running Microsoft Dynamics CRM Server:
  • configdb
  • database
  • metabase

To do this, follow these steps:

  1. On the computer that is running Microsoft Dynamics CRM Server, click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM

  3. Right-click configdb, and then click Modify.
  4. In the Value data box, change the data source to the name of the new SQL Server, and then click OK. For example, the string value in the Value data box should resemble the following:

    Data Source=NewSQLServer;Initial Catalog=MSCRM_CONFIG;Integrated Security=SSPI

  5. Follow steps 3b-3d for the database subkey and for the metabase subkey.

Notes

  • If multiple Microsoft Dynamics CRM Roles are in your deployment, you must update the registry keys for all the server roles.
  • If you use the Microsoft Dynamics CRM Data Connector for SQL Server Reporting Services and if you are not moving the SQL Server Reporting Services server, you must update the configdb subkey on the computer on which the Microsoft Dynamics CRM Data Connector for SQL Server Reporting Services is installed.
  • Configure the Microsoft Dynamics CRM Application to point to the new SQL Server and SQL Server Reporting Services. To do this, follow these steps:
  1. On the computer that is running Microsoft Dynamics CRM Server, click Start, point to All Programs, point to Microsoft Dynamics CRM, and then click Deployment Manager.
  2. Click Organizations.
  3. Right-click the organization that you moved to the new computer that is running SQL Server, and then click Disable.
  4. Right-click the organization that you disabled, and then click Edit Organization.
  5. Type the new name of the SQL Server and the new URL for the SQL Server Reporting Services server.

    Note This step publishes the reports that are in Microsoft Dynamics CRM to the new computer that is running SQL Server Reporting Services server that you specify.
  6. Click Next two times, and then click Apply.
  7. Right-click the organization that you disabled in step 4c, click Enable, and then click Yes.
  1. If you are using the Microsoft Dynamics CRM Data Connector for SQL Server Reporting Services and if you are moving to a new SQL Server Reporting Services server, you must install the data connector on the new computer that is running SQL Server Reporting Services.

Comments

Post a Comment

Popular posts from this blog

MS CRM 4.0 Relationship Mappings Error

Image
Whenever relationship is deleted but relationship attribute is used in another relationship mappings. In that case if you click on mappings you will get below error message. Cause: attribute is deleted but attribute is used in attribute mappings. In MS CRM attribute relationship mappings are saved in following tables E ntityMapBase AttributeMapBase Identify the mapping record in EntityMapBase Table. Take the GUID of that record and find the related attribue records in AttributeMapTable select * from dbo . AttributeMapBase where EntityMapId = 'place your relationship record GUID' update the your deleted attribute records DeletionStateCode with 2.
Read more

Open Data Protocol

The open data protocol is a web protocol for querying and updating data.OData does this by applying and building upon web technologies such as HTTP Atom publishing Protocol (AtomPub) JSON to provide access to information from variety of applications,services and stores. OData being used to access information from different sources like Relational Data base File Systems Content management systems Traditional  web sites OData is consistent with the way the Web Works.This Commitment to core Web Principles allow Odata enable a new level of data integration and interoperability across the broad range of clients,server, services and tools. OData provides the uniform way to expose,structure,query and manipulate data using REST practices and JSON or ATOM.OData also provides a way to reprasent metadata about the data,allowing computers to know more about the type system,relationships and structure of the data.
Read more

Using Read-only versus const

There are Two difference versions of constants in C#: the Const keyword is used for compile –time constants read only keyword is used for runtime constants. The main issue with const is that it's evaluated at compile-time, which means if it's changed at a later date; you have to not only recompile that application, but all applications that reference that application. In contrast, read -only is evaluated at run-time providing you a lot more flexibility. An overview of differences between const and read-only in c#      Const Read only Cont be static Can be either instance-level or static Value is evaluated at compile time The value is evaluated at run time. It is initialized at declaration only It can be initialized in declaration or by code in the code constructor .therefore read only fields have difference values depending on constructor used.   So, const should really only be used for logical, real-world constants such as days of week, numeric Constants, etc. as for as perfo...
Read more