G'day all:

My current DB is gettting pokey ... I want to run the Optimize utility. I have these questions.

1. Do the users need to be logged out and do I

have to close the DB from FM9 server before

starting?

2. Looks like those who set the server machine

up loaded FM9 server Admin there but didn't

load regular(client) FM9 there. I know where

to find Optimize on the normal FM9 - is it

available on FM9 server, or do I need to

load the normal product there?

3. Looks like Optimize on a local copy of the DB

runs about 50 minutes ... any feedback on how

long it should run on the server copy also

appreciated. My file is 7 GB in size.

Thanks for your assistance!

I've heard that you should not use that utility, but "Save as...Compacted" instead. You'll need a regular copy of FMPA or FMP9A to do any of that though.

7 GB is pretty big. What does the file do?

reading the manual, It advises not to do compact if the file will experience frequent changes as it may actually increase fragmentation.

The file is a database of our clients and the various notes and subrecords associated with

each one's business transactions. The main table

is huge with over 1000 fields ( they track a lot of fees and gov't paperwork).

[color:red]Do not be using these utilities.

Check server settings, especially the amount of RAM allocated to cache. Setit to the maximum it will takeon server. How much RAM is on the server?

Also, on the workstations, set the amount of RAM reserved for cache to 12MB.

Steven

Thank you. I will check that with my server guys.

Any idea why these utilities are still 'on the books'? Just so I know what they are good for, if anything. :

It was set to 64 MB on the server, with a max available of 479 MB. We set it to the max as suggested, but should we also up the cash flush distribution interval? It's currently set for 1 minute.

Read the FileMaker Server 9 Configuration Guide, it's all in there. I know it's available to TechNet members but it may also be on the FMI web site for everybody else.

Leave the flush distribution at one minute. Also, you almost do not have enough installed RAM in your server.

Steven

OK, Thank you. Haven't had any complaints since we made the adjustments suggested (other than increasing RAM) Will do that too.

How many of those 1000 fields are indexed? Lots of records + lots of indexed fields will kill performance for certain things, e.g. adding a new record.

Many, many of them are indexed. I inherited the DB so don't really understand why those who created it chose to index what they did.

If there's any good whitepapers or other sources of wisdom on indexing, please point me at them. Likely 90% of what they indexed can have that changed, but I need to understand what a change like that will do to the database.

Thanks.

Its a good idea to get a developer tool such as Inspector, Base Elements, or Documentor.

It can better display the information that can be pulled from the DDR ( Pro Advanced needed ).

Indexes are required for such things as value lists, joins (child side), etc.

FileMaker's native setting is to have indexing off on a field but with a checkmark for creating indexes when needed. ( I wish there was a system option to set this preference ).

Anyway, whenever a user click in a field and performs a find, with this option on, it will create an index.

A general rule of thumb is to index fields that will be heavily searched on as well as the ones that are required. As for the other ones that hardly ever are searched on, you should leave the indexing off. As you monitor your users' habits, you may have to tweak some of them on or off.

Thank you for the feedback. Part of what I also have to do is trim the number of fields created over the years, so this will help me with that as well.