Aug
16
2011

My first SQL 2008 error encounter – SQL 2008 Cache File Relocation

Today while debugging a C: drive disk space issue found that in certain service account location C:\Users\\AppData\Local\Temp there are several “*.CACHE” files.

They come named as follows:

“machine-name_instance.SQL-Server-name_{49268954-4FD4-4EB6-AA04-CD59D9BB5714}_#.cache”

where: “machine-name” is the server’s Windows computer name;
“instance.SQL-Server-name” is the MS SQL Server 2008 server and instance name;
“#” is some unique 1-2 digit identifier.

these were created by Data collector functionality of SQL server 2008, when you do not specify specified cache file patch in data collector properties then it may pile up several bulky cache files in service account temp default folder. So it is suggested to specify a cache path while configuring data collector. A very good article to resolve this issue is available at MS support KB article @ http://support.microsoft.com/kb/2019126

Excerpt of solution from above link:

Locate the corrupted cache file and delete it. To do this, follow these steps:

  1. Start SQL Server Management Studio, and connect to the instance of SQL Server where the error occurs.
  2. Expand the Management folder, right-click Data Collection, and select Properties.
  3. If a directory is displayed for Cache directory, this is the location of the Data Collector cache files. Go to step 5.
  4. If a directory is not displayed for Cache directory, the default cache directory is the local temporary directory of the account that executes the collection set. This account may be the SQL Server Agent service account. For example, on Windows Server 2008, if the collection set was executed by an account that is named “sqlacct,” this account’s temporary directory is located in a path that resembles the following: C:\Users\sqlacct\AppData\Local\Temp.
  5. Find all files that have a *.CACHE file name extension, and move the files to a different directory.
    If the collection set is the Utility Information collection set, do not try to run the collection set directly. Wait 30 minutes to see whether the problem is resolved. If the collection set is any other collection set, restart the collection set and learn more about other sets.

 

Download PDF

Related Posts

About the Author: Nitin Garg

Indian born, trekker, biker, photographer, lover of monsoons... I love to blog the topics I research and find useful for self or online community to save time and energy :) Everything you read on my blog is my own personal opinion!

1 Comment + Add Comment

Leave a comment

Subscribe to this blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 174 other subscribers

Translate this blog!

EnglishFrenchGermanItalianPortugueseRussianSpanish

Calender

May 2019
M T W T F S S
« Nov    
 12345
6789101112
13141516171819
20212223242526
2728293031  

View Post by Categories

%d bloggers like this: