March 26, 2010 at 11:42 am
Ok I need to load data from SQL 2005 into Great Plains, any ideas?
thank you
March 26, 2010 at 11:48 am
Get Great Plains' database schema, build a mapping document, then write the conversion in SSIS.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
March 26, 2010 at 11:51 am
Great Plains is an application which can use SQL Server as it's database.
Great Plains versions 5 through 6 offered a number of database options, including c-tree, pervasive, and MSSQL 7-2000.
At least two of my clients currently have Great Plains V8 on SQL 2005 and 2008;
so Great Plains itself is not a database system, but an application that uses a database.
can you explain or research a bit more on what you are refering to?
Lowell
March 26, 2010 at 11:55 am
I would check with GP and see if this is supported. Some systems especially accounting systems don't support direct updating of the database and you may damage data integrity.
They may have a specific import process that needs to be followed.
If it was reference data I might be tempted to go for it, but transactional data, no way.
March 26, 2010 at 12:00 pm
Yeah I'm trying to figure out whats going on here, this is my first day at work and my task is to fix
that great plains mess they have here, as far I know, they get a flat file and load it into access and then into SQL and then use a eConnect to load that data into Great Plains, not sure why yet.
I will let you know later on today.....thanks
March 26, 2010 at 3:38 pm
eConnect is the accepted GP mechanism for importing data. Good luck.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply