I don't know. Probably a dozen.

>How many concurrent users?
>
>>>>
>>>>I wonder if this limitation (very high) actually sets Max Limit to No limit (practical) and therefore causes the problem where the SQL Server stops after some time.
>>>>Which brings me to a question (to which I do not know the answer); what would you set the Maximum memory value in order to set a limit and prevent the SQL Server from stopping?
>>>
>>>Just shut down the SQL server and check how much available memory the system has then - use task manager to see that. Then set the limit to about two thirds of that. It's quite possible that the SQL engine has all the memory it may need, but the rest of the machine is starved, so the filesystem, networking etc may suffer and thus become the bottleneck. So leave some air for the system.
>>>That would be where I'd start.
>>
>>Thank you for your input and for your suggestions. So far I told the customer to reset the SQL Server; so that they can go ahead with the application (currently it was stuck and not usable). As far as memory, I told them that most likely it is the number of the Max memory set in the SQL Server that causes the problem. But I did not want to suggest to them what number to use (even though I believe you know what you are talking about). The customer is a big organization and they should have a DBA. I told them to check with the DBA and set the limit to whatever the number he/she suggests. I will see what they do and how it effect the operation.
>>Again, thank you.