Your arguments makes perfect sense to me!
Here is my 2cents:
1.2.What back-end databases does your solution work with (e.g., Oracle, Microsoft SQL Server, BDB. PostGres, MySQL)? What versions are allowable or required (e.g., Oracle 9 or 10)? Can the database backend run on the application server, or does it require a separate machine? Moodle is designer around the MySQL database. Due to some syntactical differences between the various RDBMS' it would involve some development and adjusting- the degree based on what the moodle community and others have already made available, and how large the differences are.
I didn't have the chance to run Moodle on PostgrSQL. My belief is that Moodle runs out-of-the box on PostgreSQL. It is a matter of selecting the database type during installation.
... I have heard the PostGres may offer certain performance improvements, and is a solution that a large New Zealand based Moodle partner uses.
That's right. The NZ advice to use PostgrSQL for very large (> 20'000?) installation.
I wouldn't understand, however, why someone would want to use Oracle (which is expensive) instead of mySQL (which is free) and go thru the necessary modifications as well.
The big database contenders like Oracle have their domain, financial institutes, governments, etc. Most of the public schools I know of have never seen such money
9. What provisions are there for moving user and course databases from one server to another, in case the primary server fails? Can we transparently back up the database on the primary server and restore it to a backup server?
Moving course _content_ amoung Moodle installations is a child's play.
Hardware and performance
A series of evaluation technical questions
This discussion has been locked because a year has elapsed since the last post. Please start a new discussion topic.