ESS best practices for updating the SQL source

Discussion created by user10625 on Nov 20, 2013
Latest reply on Nov 20, 2013 by user10625



We are implementing an ESS with a MySQL database (one that is, thankfully, under our control, not off in some distant department).

(We are on FMS 12, Windows server, FYI.)


We have noticed that schema changes on the SQL side don't "take" right away in FMP . . .and we are wondering, what is the best practice for this? Should you shut down FMS while making the changes? Just make sure no one's logged into FMP on the FMS?


For example, if we want to change the name of a field in the SQL Source, and that field is used in an import in FMP . . . we note that when we change the name, the field greys out in the import spec, and the "new" field [name] does not appear as an importable field.


There is probably a whitepaper/tech brief about this issue, thanks for any pointers.



Christopher Bailey


Boston, MA