NiceMan331
asked on
is Oracle the best solution for ERP
before starting as described here
https://www.experts-exchange.com/questions/28347724/i'm-going-to-build-my-own-ERP-who-can-help-me.html
, we have factory , then branches will sale its products
the software witch i review , having no links between the branches and the factory
each one have separate database , as they said to keep the operation fast & quickly
if they do linking them , the transactions will be slowly , moreover while too customers in the branches .
to do the transactions between the branches , e.g : ordering items from the factory then receiving it automatically , they have something like patch file to sent text files between each other
then some process should be done to complete receiving then posting that transactions
what do you advice ?
1-oracle or mysql ? note i never work mysql before
2-is that strategy (sending text files between the factory & branches ) is right ?
or better do linking between them , ( via internet ) ?
https://www.experts-exchange.com/questions/28347724/i'm-going-to-build-my-own-ERP-who-can-help-me.html
, we have factory , then branches will sale its products
the software witch i review , having no links between the branches and the factory
each one have separate database , as they said to keep the operation fast & quickly
if they do linking them , the transactions will be slowly , moreover while too customers in the branches .
to do the transactions between the branches , e.g : ordering items from the factory then receiving it automatically , they have something like patch file to sent text files between each other
then some process should be done to complete receiving then posting that transactions
what do you advice ?
1-oracle or mysql ? note i never work mysql before
2-is that strategy (sending text files between the factory & branches ) is right ?
or better do linking between them , ( via internet ) ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I don't believe you will find a better opinion than has already been posted. This is probably why no other Expert has posted.
To sum it up: There really is no 'best' when it comes to anything.
As far as designs go: They should be driven by requirements.
To sum it up: There really is no 'best' when it comes to anything.
As far as designs go: They should be driven by requirements.
If you're looking for more options about the platforms look around at some of the big ones that you are going to try to emulate.
Do they run on oracle, mysql, sqlserver, postgres, informix, db2, etc?
Is your project going to need to support the same level of data, users and transactions that those systems can? If so, you may want to follow their lead in platform selection.
If not, then, as above, pick something you and your team can actually work with. If you don't know how to do database development then poll your team's skills. You're going to spend a LOT of time and money (even if you work for free) getting the work done. If you're making that investment without having the skills to support it; then it's likely a huge waste of time. So, I'd always go with whatever my team can support.
For remote operations, if at all possible, I'd try to steer clear of sending files and importing them. Nearly every platform has some sort of remote communication. If connectivity is a problem then ideally it will be queue based.
These are still fairly basic answers but it's a very wide open question.
Do they run on oracle, mysql, sqlserver, postgres, informix, db2, etc?
Is your project going to need to support the same level of data, users and transactions that those systems can? If so, you may want to follow their lead in platform selection.
If not, then, as above, pick something you and your team can actually work with. If you don't know how to do database development then poll your team's skills. You're going to spend a LOT of time and money (even if you work for free) getting the work done. If you're making that investment without having the skills to support it; then it's likely a huge waste of time. So, I'd always go with whatever my team can support.
For remote operations, if at all possible, I'd try to steer clear of sending files and importing them. Nearly every platform has some sort of remote communication. If connectivity is a problem then ideally it will be queue based.
These are still fairly basic answers but it's a very wide open question.
ASKER