- Posts: 5
- Thank you received: 1
Ask the community, share ideas, and connect with other LimeSurvey users!
SELECT k.column_name field_name FROM [INFORMATION_SCHEMA].[KEY_COLUMN_USAGE] (@P1 nvarchar(4000),@P2 nvarchar(4000)) SELECT k.column_name field_name FROM [INFORMATION_SCHEMA].[KEY_COLUMN_USAGE] k LEFT JOIN [INFORMATION_SCHEMA].[TABLE_CONSTRAINTS] c ON k.table_name = c.table_name AND k.constraint_name = c.constraint_name WHERE c.constraint_type ='PRIMARY KEY' AND k.table_name = @P1 AND k.table_schema = @P2
I would prefer not to talk about test assumptions.
Looks more like a resource/config issue. But there are too many little things which can cause high loads. LimeSurvey is not the limit here, even though it might runs unoptimized SQL-queries and code. But Apache with only 8 GB RAM will be a bottleneck when trying to handle thousands of users at once.Even if you have two Apaches.And 8 GB RAM for a databaseserver is low too.Does the situation I described means for example a configuration problem or maybe the application will not allow more?
What is the relation of your post and the post of the thread-starter? For me it looks like your post is non related to the post of the user limepl.My server: