March 23, 2012 at 1:29 pm
Has anyone else had issues with a large size TokenAndPermUserStore? Microsoft is directing us to this: knowledge base article, (KB955644) .
Why are we having to manage this in SQL 2008? It seems like a bug that still isn't fixed.
The result is it basically causes the decrease in performance of queries over time. Running DBCC FREEPROCCACHE fixes the issue temporarily. Running DBCC FREESYSTEMCACHE does not.
Has anyone else had to manually configure "access check cache bucket count" and "access check cache quota" setting?
We are running on IA-64.
This has impacted and caused unacceptable level of timeouts.:angry:
March 23, 2012 at 1:44 pm
Yes this does happen in 2008 but is less common than in 2005. Here is another thread with some great resources on the topic:
http://www.sqlservercentral.com/Forums/Topic1232526-391-1.aspx
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 23, 2012 at 2:56 pm
Thanks, I will review from the link.
March 23, 2012 at 2:58 pm
There's some bits written about that in chapter 3 of this http://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/
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
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply