| 1> | | | | — it doesn’t use Windows Domain logins |
| If your company deploys Microsoft Great Plains as | | | | or even SQL Server logins. Instead it uses it own |
| corporate ERP, at some day you will come to this IT | | | | security model, built in DYNAMICS database. GP |
| routine on how to migrate your accounting/MRP | | | | security model realization for MS SQL Server platform |
| system from one physical computer to another. | | | | utilizes MS SQL Server logins (stored in master |
| As IT person you may or may not have a lot of GP | | | | database) and grants them access to DYNAMICS |
| architecture knowledge, this is why we would like here | | | | and each company databases. Additional |
| to orient you in this subject of transferring. We would | | | | complication here is this — GP user password |
| like to stress here, that this routine of transfer typically | | | | (as you enter it in GP interface when you login) is |
| is something that should be done by professional | | | | actually encrypted for your user login in MS SQL |
| consultant, so you do not have us responsible for | | | | Server — this is why you can not just use your |
| consequences if you have complications: | | | | GP user login to register GP SQL Server in MS SQL |
| customization, reports modification, complex | | | | Server Enterprise Manager |
| integrations to name a few | | | | - Installing GP on the new Server. When you are |
| - Great Plains Architecture. Microsoft Dynamics GP | | | | done with SQL installation (don’t alter sorting |
| is MS SQL Server based application. GP workstation | | | | options), you will need to install Microsoft Dynamics GP |
| connects to SQL database via ODBC, this means that | | | | with empty companies with the same companies |
| when migration is done, you should update ODBC | | | | databases ID (where you used similar GP account |
| connection settings to point out to new SQL Server | | | | structure segmenting — this is technically not |
| - GP Security Model. This is the most important part | | | | required, but will make your life easier, if something |
| in understanding the migration scenario. Great Plains | | | | goes wrong) |
| initially targeting multiple database platforms: Pervasive | | | | - Now security transfer surgery. If you feel that you |
| SQL/Btrieve, Ctree/Faircom, and MS SQL Server plus | | | | are very strong with DTS — you may use this |
| several networking platforms, such as MS Windows, | | | | tool. |
| Novell and Macintosh — and by doing so | | | | |