I don’t fully agree, sorry …
Yes, you have to pick the edition which meets your needs, but I strongly recommend to make a good forecast how the system will be in future, especially how the transaction- and data-volume will increase, how important reporting will be, and so on … You have to have in mind, that there is option available to upgrade from a Standard to an Enterprise Edition, in this case you would have to re-buy the liceses - and that’s even more expensive. So, when picking the right edition “think” into the future!
When it’s about the databses you can run on runtime: So, what’s about system related databses? E.g. databases which are used by NAV maintenance tools which have to be on the same server? These db’s are actually equal to msdb or master. What about db which contain historical NAV data, apart from the productive db, which are linked with the “real” NAV db for integrated reporting? What about db which temporary contain EDI data of external systems, e.g. orders, which are imported into NAV? There are plenty of reasons, where you have to have multiple db on the same server, e.g. to make various kinds of backups, security settings, performance, and so on.
IMO it’s absolutely not acceptable to NOT permit running those dbs on one server, because they’re all part of ONE AND THE SAME NAV SYSTEM. We have negotiated this with MS and they agreed on that point.
I have to admit, that running a POS db on the server was a bad example, as here the primary usage is not NAV related … so, as stated: it’s a matter of argumentation: ask you local MS/MBS partner!