I have a question regarding the same topic. What if we are going to implement NAV in a retail environment, which may require to have HQ and store databases? HQ database will definitely need to use SQL server, but what about the stores?
This is one of the few cases where the Native DB still has a place. The major advantage is that you just install the DB and it works. you don't even need a server. For these applications you want it to be as simple as possible.
I think in the short term Products like LS retail will have the POS stations runnign on NAV 2009 Classic, and the Back Office running on the latest RTC version. Then in the future clients will switch to a dedicated client that has nothing to do with Navision. In fact the idea of using Navision as a POS client has no real sense these days, and is there only for historical reasons.
Comments
This is one of the few cases where the Native DB still has a place. The major advantage is that you just install the DB and it works. you don't even need a server. For these applications you want it to be as simple as possible.
I think in the short term Products like LS retail will have the POS stations runnign on NAV 2009 Classic, and the Back Office running on the latest RTC version. Then in the future clients will switch to a dedicated client that has nothing to do with Navision. In fact the idea of using Navision as a POS client has no real sense these days, and is there only for historical reasons.