I know this topic has been discussed
here but I haven't seen it answered. Andour case has an interesting twist on it, too (read on.)
We have a Windows service, which we configured to be dependent on the SQL Server service, and our service make queries when starting.
We are very often hitting the issue that even though SQL Server has started, it is not ready to accept queries (apparently, the database nust be started too, and SQL Server reports that it is running before that happens).
We implemented a wait in out service, to wait and retry until the first query succeeds. It usually does on the second try (after 10 seconds wait). We thought we were in the clear, but what happened next is this (only on some systems, not all users see this):
- The first SQL query is a very simple query, returning only a f ...
Go to the complete details ...