MSCRM 迁移 数据库 服务器

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 2011 on the existing server

    1. Back up the OrganizationName_MSCRM database and the MSCRM_CONFIG database. To do this, follow these steps:

      1. On the computer that is running Microsoft SQL Server, click Start, point to All Programs, point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.
      2. In the Connect to Server window, type the name of the server that is running Microsoft SQL Server 2008 in the Server name box and then click Connect.
      3. Expand Databases, right-click the OrganizationName_MSCRM database, point to Tasks, and then click Back Up.
      4. Under Destination, add the location to save the backup file, and then click OK.
      5. 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 OrganizationName_MSCRM database and the MSCRM_CONFIG database on the new computer that is running SQL Server. To do this, follow these steps:
      1. On the new computer, click Start, point to All Programs , point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.
      2. In the Connect to Server window, type the name of the server that is running Microsoft SQL Server 2008 in the Server name box and then click Connect.
      3. Right-click Databases, and then click Restore Database.
      4. Under Destination to restore, type the name of the OrganizationName_MSCRM database in the To database box.
      5. Under Source for restore, click From device, click the ellipsis button ( ... ), add the OrganizationName_MSCRM database, and then click OK.
      6. Click to select the Restore check box, and then click OK.
      7. 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.

    3. Update the configdb registry subkey on the computer that is running Microsoft Dynamics CRM Server 2011. To do this, follow these steps:
      1. On the computer that is running Microsoft Dynamics CRM Server 2011, click Start, click Run, type regedit in the Open box, and then clickOK.
      2. Locate 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= <NewSQLServeName>r ;Initial Catalog=MSCRM_CONFIG;Integrated Security=SSPI
      Note
      If multiple Microsoft Dynamics CRM roles are in your deployment, you must update the configdb registry key for all the server roles.

      If you use the Microsoft Dynamics CRM Reporting Extensions and if you are not moving the Microsoft SQL Server Reporting Services server, you must update the configdb subkey on the computer on which the Microsoft Dynamics CRM Reporting Extensions are installed.

    4. Configure the Microsoft Dynamics CRM application to point to the new SQL Server and Microsoft SQL Server Reporting Services. To do this, follow these steps:
      1. On the computer that is running Microsoft Dynamics CRM Server 2011, click Start, point to All Programs, point to Microsoft Dynamics CRM 2011 , 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 Microsoft SQL Server Reporting Services server.
      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.
    5. If you are using the Microsoft Dynamics CRM Reporting Extensions and if you are moving to a new Microsoft SQL Server Reporting Services server, you must install the Microsoft Dynamics CRM Reporting Extensions on the new server that is running Microsoft SQL Server Reporting Services.
时间: 2024-11-03 21:19:06

MSCRM 迁移 数据库 服务器的相关文章

Ubuntu中开启MySQL远程访问功能,并将另一个数据库服务器中的数据迁移到新的服务器中

一.开启MyS远程访问功能 1.进入服务器输入netstat -an | grep 3306确认3306是否对外开放,MySQL默认状态下是不对外开放访问功能的.输入以上命令之后如果端口没有被开放就会显示 <strong>显示结果:tcp 0 0 127.0.0.1:3306 0.0.0.0:*LISTEN</strong> 2.从上面的显示结果可以看出,mysql的3306端口只是监听本地的连接,这样就阻碍了外部ip对该数据库的访问,这样就需要修改mysql配置文件, 输入vim

使用rman迁移数据库到异机

迁移数据库的方法有多种,较为常用的则是使用RMAN来迁移.使用RMAN迁移数据库属于数据库的物理备份与恢复范畴,整个过程中数据库的相关信息是完整地镜像.因此,基于此种方式还原恢复的数据库用于测试会使得与真实的生产环境差异相对较小. 一.主要步骤     1.备份数据库     2.拷贝备份到目的服务器     3.为目标数据库创建项目目录     4.为目标数据库创建pfile或spfile(使用RMAN还原或复制原pfile到目的服务器)     5.还原控制文件     6.还原数据文件  

关于Laravel 迁移数据库的问题

今天在Homestead 中用 php artisan migrate 迁移数据库时出现了拒绝的情况: 科学上网之后发现只要修改项目文件夹下面的database.php 和.env 文件中的数据库配置,要保持一致,如下图 然后记得重启服务器,因为我是在Homestead里面部署项目,所以用以下命令可以重启服务器 cd ~/Homestead && vagrant provision && vagrant reload 然后运行vagrant ssh 进入Homestead中

linux 下 jira-6.3.6 配置 破解 翻译 迁移数据库

各个版本翻译包下载地址  https://translations.atlassian.com/dashboard/download jira下载地址  https://www.atlassian.com/zh/software/jira/download 这里使用的是最新版本jira-6.3.6 实验环境 操作系统 Red Hat Enterprise Linux Server release 5.9 (64) 数据库 mysql : Ver 14.14 Distrib 5.6.12, for

数据库服务器改名导致Reporting Service不可用的案例

案例环境: 操作系统版本    :    Windows Server 2012 R2 Standard 数据库版本      :   SQL Server 2012 Standard Edition SP2 案例介绍: 其实已经是第二次碰到这种情况,还是决定将这个案例记录一下.第一次是做数据库迁移时碰到,没有时间整理记录,第二次准备一个测试环境,从虚拟机一个服务器克隆了一个测试服务器GETESTNT30, 服务器名称变了,但是SQL SERVER里面@@SERVERNAME 与 SERVERP

检查mysql主从同步结构中的从数据库服务器的状态-脚本shell

检查mysql主从同步结构(一主一从)中的从数据库服务器的状态          (ip授权.从服务器和IO是否正常.从mysql进程是否正常) 主mysql: 192.168.1.10 从mysql: 192.168.1.20 [[email protected] ~]# vi check_slave.sh #!/bin/bash master=192.168.1.10 i=1 service mysqld status &>/dev/null while [ true ] do echo

用MyEclipse10.0远程连接Mysql数据库服务器

说明:本文档所有的操作均在满足以下条件的情况下操作, A.远程Linux服务器已经安装好MySQL数据库 B.本地电脑可以ping通远程服务器 C.已经成功安装了Myeclipse 一.下载mysql-connector-java-3.1.14-bin.jar 这个是连接mysql数据库的驱动器. 下载地址: http://dev.mysql.com/downloads/connector/j/5.0.html 也可以到官方网站下载,网址如下:www.mysql.com 二.在Myeclipse

MySQL数据库服务器搭建及基本管理

1.安装MySQL数据库 从官网下载RPM包:http://dev.mysql.com/downloads/mysql/ 选择适用于当前系统的bundle集合包 [[email protected] 桌面]# tar -vxf MySQL-5.6.15-1.el6.x86_64.rpm-bundle.tar -C /opt/mysql/ MySQL-shared-5.6.15-1.el6.x86_64.rpm   //共享库 MySQL-devel-5.6.15-1.el6.x86_64.rpm

简单说说THP——记一次数据库服务器阻塞的问题解决

背景:公司某个大型业务系统反馈最近数据库服务器总是宕机(此处描述不准确,后面解释),最后,客户.运维人员都觉得实在是忍无可忍了,项目经理打电话找到我问是否能帮忙诊断一下,刚好第二天要去现场沟通另外一个系统的测试需求,于是答应第二天顺便看一下.------------------------------------ 排查解决过程:第二天来到现场,正在沟通需求的时候,运维人员突然说,操作又开始卡了,于是连上服务器,先用top大概看了一下资源的使用情况,此时CPU已经基本上满载了,而且可以发现用户态的