2 Replies Latest reply on Oct 8, 2012 9:49 AM by CarstenLevin

    Running Reports on Server 11.0v3 freezes up all other users


      Server Experts. Vexing Problem (2): Background: “My client runs call centers. 10 reps in a call center may be equivalent to 30 or 50 reps on other applications because the rep is entering data and flipping layouts continually throughout her shift.” My client cannot run reports while reps are working. “These large reports caused not only coffee cups but the whole application to freeze for the duration of running the report. This was primarily with the Fixed Reports which can take up to 45 minutes to run and export to excel. Reps would get blank screens, their systems would lock and/or the coffee cup during the full process.”


      Question 1: This client runs very few FileMaker reports with sub-summary and grand summary data. Instead the application gathers data from every data record and sets it in a report table where it is crunched and exported to excel. This takes a long time. What is your experience in running long reports; do they slow down the other users? Will an upgrade to Server 12 solve this problem?

      Question 2: If we find an answer to the backup problem (1) then we could pull a backup copy to run reports. My client has found that these reports run much faster on FileMaker Pro 11 than on Server 11. Is this your experience?

      Are there other work-around solutions that you know about and have tried?

        • 1. Re: Running Reports on Server 11.0v3 freezes up all other users

          It would seem to me that the server hardware is not up to the task.  Running heavy reports will affect the workstation where it is run on,but it should not affect other connected clients in the manner that you're reporting.  Can you specify what kind of hardware and OS you're running?


          Also can you expand on the reporting mechanism, are you collecting a lot of data from unstored calcs?

          • 2. Re: Running Reports on Server 11.0v3 freezes up all other users

            It might be as Wim is concluding. A hardware problem.

            But it could also be due to bad database design (data architecture).


            • How large data sets is involved in your sub-summary and grand summary's?
            • Are the data behind the summaries locally stored or related?
            • Are there some interesting calculations behind the fields used in the summaries.


            There are methods to ensure that the data used in the summaries etc.etc. are stored (versus unstored). And this may very well be the issue.


            The easy way is to make sure that the hardware and the configuration is OK (please see my question about your configuration in my answer to your backup question).

            Best regards