Partner Only Article

Article ID

:

884598

Last Review

:

2005-08-01

Revision

:

3.0

1.

Install Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Service Pack 3 (SP3) on the new server.

When you install MSDE 2000 SP3, use the same sort order that you used on the old server. You can find the sort order by running the following script in the Support Administrator Console against your master database.

sp_helpsort

Note The MSDE 2000 SP3a CD was included with the Microsoft Great Plains Standard CD.

2.

Use the Support Administrator Console to run the Capture_Logins_MSDE script against the DYNAMICS database on the old server.

To obtain the Capture_Logins_70_MSDE script, visit the following Microsoft Web site:

https://mbs.microsoft.com/downloads/customer/TK33331-capture_logins_msde.txt

3.

Back up the DYNAMICS database and the company databases on the old server. There are two methods you can use to back up the databases.

Method 1

Method 2

You can run the following script in the Support Administrator Console.

BACKUP DATABASE TWO

TO DISK = 'C:\Great Plains\Backup\TWO.bak' WITH INIT

In the script, replace the following placeholders with the correct information:

Note This script overwrites existing files that have the same name if files already exist in the backup location.

4.

Copy the backup file from the old server to a local drive on the new server.

5.

Set up an ODBC connection at the new server that points to the new server. Also, create an ODBC connection that points to the new server on all the client workstations that have Microsoft Great Plains Standard installed.

6.

On the new server, install a client/server installation of Great Plains Standard, and then create a new DYNAMICS database by using Great Plains Utilities.

Make sure that you use the same account framework that you used on the old server. If you are not sure, run the following script in the Support Administrator Console to determine the account framework.

select * from DYNAMICS..SY003001

select * from DYNAMICS..SY00302

Use the following values to determine the account framework:

7.

Use Great Plains Utilities to create the new company databases on the new server. Give each database the same database name, company identifier, and company name that you used on the old server. You can verify the DB/Company ID and Company Name on the old server by running the following statement in the Support Administrator Console:

select INTERID,CMPNYNAM from DYNAMICS..SY01500

In the console results, the INTERID field represents your DB/Company ID and the CMPNYNAM field represents your Company Name. Use these values when you create the new company databases on the new server.

8.

In Great Plains Standard, restore the DYNAMICS database and each company database from the backup file that you created in step 3.

Restoring to the same location on the new server

There are two methods that you can use to do this if you are restoring the databases to the same location on the new server that you used on the old server.

Method 1

Method 2

Restore the databases by using the following script:

RESTORE DATABASE [TWO]

FROM DISK = 'C:\Great Plains\Backup\TWO.bak' 

WITH FILE = 1, NOUNLOAD, STATS=10, RECOVERY

In the script, replace the following placeholders with the correct information:

Restoring to a different location on the new server

If the location of the database files on the new server is different from the location of the database files on the old server, you must restore the files differently.

For example, if the database files were located on the old server at D:\Program Files\Microsoft SQL Server\MSSQL\Data, and if the database files are located on the new server at C:\Program Files\Microsoft SQL Server\MSSQL\Data, you must follow these steps to restore the backup.

9.

Repeat step 8 for each database.

10.

Use the Support Administrator Console to run the Drop_User_DYNAMICS_MSDE script against the DYNAMICS database on the new server. This script works for both Microsoft SQL Server 7.0 and Microsoft SQL Server 2000.

To obtain the Drop_Users_DYNAMICS_MSDE script, visit the following Microsoft Web site:

https://mbs.microsoft.com/downloads/customer/TK33331-drop_user_dynamics_msde.txt

11.

Use the Support Administrator Console to run the Drop_User_Company_MSDE script against each of your company databases on the new server. This script works for both Microsoft SQL Server 7.0 and Microsoft SQL Server 2000.

Note You must replace %Companydb% with your company database name for this script.

To obtain the Drop_Users_Company_MSDE script, visit the following Microsoft Web site:

https://mbs.microsoft.com/downloads/customer/TK33331-drop_user_company_msde.txt

12.

Use the Support Administrator Console to run the Create_SQL_Logins_MSDE.sql script against the DYNAMICS database on the new server.

To obtain the SM_Create_SQL_Logins_MSDE.sql script, visit the following Microsoft Web site:

https://mbs.microsoft.com/downloads/customer/TK33331-create_sql_logins_msde.txt

13.

Use the Support Administrator Console to run the Add_Users_Company_MSDE script against each of your company databases on the new server. This script works for both Microsoft SQL Server 7.0 and Microsoft SQL Server 2000.

Note You must replace %Companydb% with your company database name for this script.

To obtain the Add_Users_Company_MSDE script, visit the following Microsoft Web site:

https://mbs.microsoft.com/downloads/customer/TK33331-add_user_company_msde.txt

14.

Use the Support Administrator Console to run the GRANT70.SQL script against the DYNAMICS database and against all the company databases on the new server. This script works for both Microsoft SQL Server 7.0 and Microsoft SQL Server 2000.

To obtain the Grant70.SQL script, visit the following Microsoft Web site:

https://mbs.microsoft.com/downloads/customer/TK7132Grant70-6.txt

15.

Install any third-party products or additional components that are required on the new server, such as Human Resources and Fixed Assets.

16.

If the Reports and Forms dictionaries were shared on the old server, move them to the new server. You can determine whether the Reports and Forms were shared by viewing the Dynamics.set file on a client workstation where Great Plains is loaded. Right-click the Dynamics.set file, and then click Edit.