Question on GP databases, prepartion of SQL database, and conversion

[hav0k1]

Hi all,

I am preparing to move an access database over to SQL to use as the backend data storage for great plains. I have limited knowledge of this product (currently studying the documentation), and was wondering about the most efficent way for an access conversion. My current database has several complex queries, which seemed to be handled by great plains modules already, which is good. However, when I set up my testing enviroment I spent several hours trying to merge the access data into the GP DB by using the "integration manager". There I set the source as the backend.mdb and the destination as my "test" database, not the dynamics one, but the company DB. However, only my customer numbers transfered, no names etc. My plan has changed now though, as I am doing a network tear down and rebuild, so I was wondering if anyone had any idea of what format etc. they would use with great plains, as well as any advice/tips on the conversion process. Thanks!

 

[jazgeek]

Your question is too vast to answer. There are well over 1000 tables in GP not to mention data conversions etc.

I've been working with this software since version 3.15 and I only know about 50 tables intimately.

I do suggest you get someone with a working knowledge of the tables and data structure to help you with this task. It may cost a bit up front, but you'll thank yourself later for not missing something.



-----------
and they wonder why they call it Great Pains!

jaz

 

[clicker666]

IMHO:

I agree with Jaz. I would hire someone familiar with Integration Manager to do the conversion. Take notes. In the future you'll be armed with the knowledge you need, and only had to pay for it once.