Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Filemaker Invoicing Database is Laggy
- Thread starter machtenx
- Start date
" I clean it up besides just backing up records? "
u dont 'clean' anything but backing it up! u just secure your self from data loss....
u need to 'purge' your records....meaning delete them based on age or some other criteria
it could be a bad design also....do u have images in records?
> need more info?
:: don't click HERE ::
u dont 'clean' anything but backing it up! u just secure your self from data loss....
u need to 'purge' your records....meaning delete them based on age or some other criteria
it could be a bad design also....do u have images in records?
> need more info?
:: don't click HERE ::
Do you have MDM (MetaData Magic) or some other analytical tool? Try using that to determine if you have bad file references or lots of unused calculated fields, or fields that have indexing turned on needlessly. Remove any stuff like that that you can, and then remove records that have been archived.
Hope that helps!
Hope that helps!
- Thread starter
- #4
Oh, I'm sorry, by backing it up I was thinking in my mind purging as well. what is a good way to perform a purge? manually is probably best? or through scripting? There are no images in the records.
I dont' have Metadata Magic, will have to look into those kind of softwares.
I dont' have Metadata Magic, will have to look into those kind of softwares.
I would probably go the the scripted sort and delete...
eg.
Delete all records where Creation_Date >"2 yrs"
or if u like to "save the history" then do an export of found set and then purge....depends on the structure and how easy/hard it would be to decide what to purge.
eg. you would not want to purge your "customer records" while you would purge "lineitem"...anyhow, you get the idea!
All the bet!
> need more info?
:: don't click HERE ::
eg.
Delete all records where Creation_Date >"2 yrs"
or if u like to "save the history" then do an export of found set and then purge....depends on the structure and how easy/hard it would be to decide what to purge.
eg. you would not want to purge your "customer records" while you would purge "lineitem"...anyhow, you get the idea!
All the bet!
> need more info?
:: don't click HERE ::
I assume your DB is large and volatile?
Try saving a copy as "copy of current file (smaller)". This can provide dramatic performance improvements if your DB is very large and volatile.
Do you have complex and/or numerous calculations that keep getting updated?
How big is your RAM? Are you running other applicatins?
Was the DB ever fast? If so, what's changed?
Cheers,
Paul J.
Try saving a copy as "copy of current file (smaller)". This can provide dramatic performance improvements if your DB is very large and volatile.
Do you have complex and/or numerous calculations that keep getting updated?
How big is your RAM? Are you running other applicatins?
Was the DB ever fast? If so, what's changed?
Cheers,
Paul J.
- Status
Similar threads
- Locked
- Question