1 / 2

Microsoft Great Plains Migration from One SQL Server to Another

Microsoft Great Plains has tens thousands of installation across the USA as well as in Australia, New Zealand, Spanish speaking South America, UK, Poland, Middle East and South Africa.

satishkartan
Download Presentation

Microsoft Great Plains Migration from One SQL Server to Another

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Microsoft Great Plains Migration from One SQL Server to Another Microsoft Great Plains has tens thousands of installation across the USA as well as in Australia, New Zealand, Spanish speaking South America, UK, Poland, Middle East and South Africa. It is on the market since 1994 when Great Plains Software released its Graphical Mac and Windows based Accounting system – Great Plains Dynamics. Now, in post- recession time we see thousands of clients world-wide are without support or as Microsoft Business Solutions names them – orphan clients. Our goal here is to educate IT department or general IT consultants to self-support Microsoft Great Plains. Today’s topic is how to move Microsoft Great Plains (old names – Dynamics and eEnterprise) from one Microsoft SQL Server to another. 1) Microsoft Great Plains Security Model –Currently Great Plains has user IDs stored in Great Plains tables as well as on the level of Microsoft SQL Server 2000 (or 7.0). Look at the Logins for the SQL Server, hosting Great Plains – you will figure out that all the GP users are Logins. And they are stored in Master database. Now if you look at Company database (TWO database, for example) – you will find users on the database level – these users have the same names as logins on the system level, plus you will find DYNGRP – this is the role on the company database level. 2) Security Migration –Now you see that if you just install SQL Server on the second computer and restore DYNAMICS and company databases from their backup – SQL Server system logins and their security will be lacking. If you feel comfortable being MS SQL DBA – you are good to use MS SQL Server Data Transformation Services to import security information from the old server. If not – then you need to use confidential (you should have Microsoft Business Solutions annual

  2. support plan) scripts to migrate Great Plains security information or call Microsoft Great Plains consultant. 3) Recommended Steps –Satish Kartan an SQL Server specialist recommends you to install MS SQL Server, then install exactly the same Great Plains environment with the same companies IDs and GL account segment structure/sorting (empty companies). At this point you are ready to restore DYNAMICS and all companies from their backups – do it. And finally – you need to transfer security – if you want DTS way – go ahead – should work. If you are not comfortable with DTS and have MBS support, login to Microsoft Business Solutions customer support section and find tech-knowledge #878449: “How to transfer Great Plains and Microsoft SQL Server 7.0 or SQL Server 2000 to a new server” with capture_logins, drop_users_dynamics and other scripts and follow the instructions To learn more, please visit here: http://satishkartan.strikingly.com/

More Related