![]() He holds FileMaker certifications for Versions 7 through 11, is a FileMaker Authorized Trainer, has presented at DevCon, conducted roundtable sessions at Pause On Error, and written for FileMaker Advisor Magazine. Subsequently he spent time in a Silicon Alley startup before beginning full-time FileMaker development in 1998, first at EnglishComp and then as an independent developer.Ĭolin has been with IT Solutions Consulting since 2005, where he is currently a Project Manager in the Application Development department. He built his first FileMaker database in the front office of a woodshop in 1994. Delivering container data via HTTP streamingĬolin Keefe holds an MFA in Sculpture from Cranbrook Academy of Art. ![]() Understanding and implementing external container data storage.Understanding, configuring and restoring from progressive backups.Full backup functionality changes (hard links).In this session from the 12 Days of FileMaker 12, we explore The only caveat is to test the functionality of the new database before deploying it to production (just in case).įiled Under: Relational Design Tagged With: Container fields, FileMaker 12, Performance 12 Days of FileMaker 12: Server File ManagementĬhanges in FileMaker Server 12’s backup scheme and the new ability to store container data externally offer significant improvements in data protection, performance and data delivery to the user. Of course, you have to upgrade to FileMaker 12 to take advantage of this new feature. Stop embedding documents in your database! It increases the file size unnecessarily and creates the negative effects mentioned above. Moving the container data to external storage reduced the file size by 99% (2.3GB to 3.4MB) Each record stored multiple images and PDFs that were not optimized. By moving the container data to external storage, the database size was reduced 46.5% (750MB to 400MB).įor the second database, there were twelve container fields in one table with 750 records. For the first database, there was one container field in one table with 68K records. It then compressed the database to reclaim the unused space. FileMaker Pro started moving the documents in the container fields to a folder called “Files” outside the database. (You could also use BaseElements or Inspector to search by field type.) For each container field, I changed the storage option to “Store container data externally” under Field Options.įinally, I closed the Manage Database window to save the changes. Next, I went through each table looking for the any container fields. Next, I opened the database and sorted the field list by “field type”. Fortunately, FileMaker 12 has a new feature called Enhanced (or external) Container Fields to address this.įor each database, I converted it by dragging the file onto the icon for FileMaker 12 and going through the automatic conversion process. The disadvantages of a large database in FileMaker are several including slower performance (more data to push over network), lower productivity (long wait times during backups), and greater risk (more susceptible to corruption in the event of a crash). The result in each case was database bloat-a file size much larger than necessary (1GB or greater). Both customers were embedding documents in the database by inserting them into container fields. Recently, I converted two customer databases from FileMaker 11 to FileMaker 12. Opening files in FileMaker Pro that were removed by the FMS admin console.Opening backup files in FileMaker Pro - ie, not hosted by a server.Uploading FMP12 backup files with the FileMaker Server admin console.FileMaker Server 12 Configuration Guide (also found at TechNet)Ĭircumstances where external container data will break (container fields will show files as missing):.Using Container Fields in FileMaker 12 (log in to FileMaker TechNet to download).In case you need to get some basic knowledge about FileMaker Server 12 and the new features related to backup and enhanced container fields, here are some great resources to get you started: Understanding these situations will help you properly restore FileMaker 12 files that use external container storage. In the course of my work on a customer project, I discovered that the links to externally stored container fields with a FileMaker Server 12 backup can break if the backup is not restored properly. After trying a number of different scenarios, I have come up with a list of circumstances where container fields will remain intact and when they won’t.Īll examples are using a Windows based FileMaker server and apply equally to both secure and open external container storage.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |