Is there any written or real world guidelines regarding performance.

We have a database that has been converted from v3 to v8.5. It could use a complete redesign for performance reasons and will eventually happen, but looking for quick win performance boosts.

I can use Advanced and create a single file version of it (instead of 5 related files) by importing the tables and fixing relations, etc.,

Question: Is there a noticeable difference in performance with a single file solution compared to a multiple file (same files, same calcs, etc., etc.)

? Just wondering if it's worth the effort or if I should just start rewriting....

Any insight would be appreciated.

If given the chance, would I rewrite ...but the size of the task could dissagree?

But if the solution stems back from fm3 is there a lot which could benefit from a rewrite, need I say tunneling of values between tables, earlier on was herds of constants and global values responsible for this ushering.

A lot of things done back then with scripts calling each other are now optained optained by a single line of script due to the theta join relation types.

Craftier relations definition can make a lot of fields not needed!

--sd

Except for the overhead of having more scripts and fields in a multi-file solution, there's not really a performance advantage one way or the other. But having your tables in one file can make it easier to manage the schema and the security. If the solution gets pretty large (say over 25 tables), then there are maintenance advantages to having tables separated into different files (modules).