Activity overview
Latest activity by MWalton
Hi, I ran into a similar issue this past week after restoring a database from Veeam to our SQL Server 2019 Availability Group. We are using RedGate SQL Monitor Version 12.1.60. Similar to others, I saw the error every 10 minutes. I temporarily disabled my alerting for this error until today when I stumbled on this thread. Here is how I fixed it with help from this thread: 1) I used the SQL Server error log to identify the spid for the last "Could not find database" error. For example, " Source spid85
Message Could not find database ID 84, name '84'. The database may be offline. Wait a few minutes and try again. "
2) I looked at the activity monitor from SSMS and identified the current login for that SPID, which unsurprisingly was the SQL Monitor domain login used to connect to the SQL Server AG. More useful was that I could identify the database that was in use as well, which in this case was 'tempdb'. (I assume this is the default database used by the application to gather stats for the instance...pardon me if this is common knowledge). 3) I then executed the following database-only equivalent to they system-wide DBCC FREEPROCACHE Note: the number in parentheses is the tempd's dbid from sys.sysdatabases: DBCC FLUSHPROCINDB (2) 4) I waited for the next 10 minute interval to come and I no longer saw the error message. 5) I re-enabled my alert for the error 21. I hope this helps others who have seen this with SQL Server 2019. Good luck, Matt / comments
Hi,I ran into a similar issue this past week after restoring a database from Veeam to our SQL Server 2019 Availability Group. We are using RedGate SQL Monitor Version 12.1.60. Similar to others, ...