June 9, 2011 at 7:02 am
hi guys,
dialy i am monitoring the sql server errorlog.In the error i got information
.this is server used in logshipping secondary server.when log backups are restored.i am seeing the information on error log.
SQL Server has encountered 16 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
SQL Server has encountered 16 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
SQL Server has encountered 16 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
Regards
venkat
June 9, 2011 at 7:10 am
Restores, including log restores, clear the plan cache.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 9, 2011 at 11:02 pm
Hi Gail,
Use DBCC FREEPROCCACHE to clear the plan cache carefully.But i'm getting dialy same information from error log.Is it critical
Regards
venkat
June 10, 2011 at 3:16 am
Gail already told you what was happening. Restores will clear the plan cache. The fact that this is a secondary log shipping server means that every time a log is restored, the plan cache gets cleared. This is normal procedure for SQL Server, not a critical error.
Are you having specific issues that are causing you concern, or are you just confused because the log messages sound horrible? (Microsoft loves phrasing their log messages in a way that causes panic to those who have never seen them before.)
June 10, 2011 at 3:36 am
kvr1985 (6/9/2011)
But i'm getting dialy same information from error log.
Yes, you will because every single restore you do will clear the cache. Hence those messages are totally normal on a log shipping secondary (which is the target for frequent restores) Is there a problem you're trying to solve here?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 13, 2011 at 5:40 am
Hi Gail,
Thank you for the replied.How can we solve the issue.Could you please provide the solution.
Regards
venkat
June 13, 2011 at 5:46 am
kvr1985 (6/13/2011)
Hi Gail,Thank you for the replied.How can we solve the issue.Could you please provide the solution.
Stop restoring to the server.
Literally, that's the only way to "solve" the issue.
You do understand that this is NOT a problem, right? This is normal. You don't have an issue. You have nothing to be concerned about. Stop stressing about it. Things are fine.
June 13, 2011 at 5:47 am
Stop restoring backups.
However that's stupid, seeing as the machine is a log shipping secondary.
Again I'm going to ask, is there a problem you're trying to solve here?
You will ALWAYS see this message frequently on servers that are configured as log shipping secondaries as the whole point of a log shipping secondary is to have transaction log backups restored on a regular basis, and each restore will cause a cache flush.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 13, 2011 at 6:31 am
Hi Gail & Brandie,
Now i understood the issue.Thank you the great answer
Regards
venkat
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply