We have a website in development, which, when we deployed it to the client production server, after a couple of hours, we began to receive request timeouts.
This was with one user who tested it on our server (which is identical in terms of the Sql Server version number - 2005 SP3), we never had the same problem.
One of our senior developers encountered similar behavior in the previous task, and he ran a request to manually update the statistics, and the problem magically disappeared - the request returned in a few milliseconds.
After a couple of hours, the same problem arose. So, we again manually updated the statistics, and again the problem disappeared. We checked the database properties and, of course, automatically updated the statistics.
As a temporary measure, we set the task to periodically update statistics, but this is clearly a bad decision.
The developer, who previously encountered this problem, is sure that this is a problem of the environment - when it happened for him earlier, after a few days it went for granted.
We looked at installing a SQL server on our db server, and this is not what I think is normal. Although they have SQL 2005 (and not 2008) installed, there is an empty "100" folder in the installation directory. There are also MSQL.1, MSQL.2, MSQL.3 and MSQL.4 (where executable files and data are actually stored).
If someone has ideas, we will be very grateful - I believe that instead of not updating the statistics, they somehow become corrupt.
Many thanks
Tony