Hello,

After upgrading from 2.73 to 3.x (currently at 3.14.5), the "Check data integrity" option doesn't work anymore in our Limesurvey installation. This is a rather big instance, with more than 3800 surveys. When clicking on "Check data integrity", the spinning wheel goes on for a while and the results page never comes up, finishing with a blank screen and nothing logged on the browser console. It worked fine when we were running 2.73.

Has anyone else experienced this? Is there any non-TTW way to perform this data integrity check?

Thanks!!!

G

gslines wrote: This is a rather big instance, with more than 3800 surveys. When clicking on "Check data integrity", the spinning wheel goes on for a while and the results page never comes up, finishing with a blank screen and nothing logged on the browser console.

I don't think such amount of surveys is used as testcase during development.
Please open a bugticket.
As a workaround you might check the php timeout and raise the limit.
I'm not aware of a commandline php controller for such tasks (perhaps a feature request).

Thank you jelo. I will open a bug ticket about it and hopefully it can be reproduced somehow by the developers.

I will also see if raising the php timeout limit gets me through it.

Thanks again!

I am quite sure that the problem lies in the long execution of the pure amount of surveys.

There are a few points in PHP where you might actually get stuck. Execution time most probably, because checking 3800 surveys will take quite a while for the script. Maybe also file size of the session and max vars or something. All things for which you might run into limits set on your server.

And I agree, I don't know the size of the installations of Limesurvey Professional for each server, but 3800 surveys is A LOT.

holch wrote: And I agree, I don't know the size of the installations of Limesurvey Professional for each server, but 3800 surveys is A LOT.

LimeSurvey is not multitenant. LimeSurvey professional installations are having a database per useraccount. Many small databases instead of one big database.

So you mean the LS Professional Installations are modified?

holch wrote: So you mean the LS Professional Installations are modified?

No, but perhaps i didn't understood your remark about the LS professional installations.

I thought you mentioned it, because of the amount of surveys which can reside on one server.
3800 users (limesurvey.org account, not Surveyusers) with one survey will result in 1 survey per database. The check of data integrity will be quick.

LimeSurvey.org account vs. LimeSurvey user might be the source of confusion.
The LS software on the professional installations is modified in many ways.
But not in terms of database per installation.
When you buy a LS professional installation you're running your own, separate php application with a separate database.

Multitenant software(which is used by many other saas survey systems) is not using one database per useraccount and is running one code for all users.

I was aware that LS runs one complete LS instance per account, which creates a lot of overhead, I guess.

On the other hand, this also means that the installations are well separated, which has its advantages too. But hey, not my problem anyway.

I now get what you were trying to say. All clear. And yes, taking this into account, even Limesurvey Professional installations probably have not been tested with 3800 survey. But then, who knows?

Checking data integrity for 3800 surveys should be ok, just update the PHP configuration of your server.

@LouisGac: Do you mean raising the php timeout setting? Others?

Yes.

OK, I'll give that a try and come back with a followup.

PS: We have more than 700 user accounts on our Limesurvey instance. Having a model of 1 separate LS instance per user is not sustainable for us.