Just wandered how many people actually have any production sites running MGE. We use MG6.3 heavily and based on my assessment of MGE so far, I'd be very reluctant to migrate our live applications.
There are a number of reasons:-
1. ODBC data provider seems to be very slow. This has been commented on by others in this and the OSGeo forum. The problem increases hugely if an ODBC data source is used in a secondary join to another feature (SDF). As a comparison, to turn on a layer, select an object and view the properties, then turn it off, it took 6 secs with an SDF-only layer, 22 secs ODBC-only layer, 78 secs with an SDF-joined to ODBC.
2. SQL Server data provider only allows layers to be created if the data in SQL has been created with Map 2007 (as far as I can tell). What if the SQL data already exists? Haven't managed to successfully display a layer based on an SDF joined to a SQL Server data provider.
3. No support for reading views/queries in databases.
4. Memory leaks. I suspect these have been addressed in the Open Source version 1.0.1 and in the upcoming service pack, but for now they exist.
5. Mapagent application errors. On the server, Windows reports unhandled exception errors. Don't know what event has lead to these. May have been fixed as above.
On the whole, I like where MGE is going. It performs well (given limited testing) with SDF based layers. It looks good and the fact that a plug-in is not required is a big plus. However, I don't think it's ready yet for production. Any body else like to comment on this?
Keith