DB files set to Archive?
-
Does anyone know what in the OS or SQL Server causes a file to be set "Ready for Archiving" when no users have touched the file? I ask because I've noticed this attribute getting set on our database files (logs and data files both), but it's not consistant. It doesn't get set on every database.
For example, yesterday I created a brand new database on our Dev box. This morning, the file attributes say it's set to "A" (Ready for Archiving). Now I know for a fact no one has touched this. And I've seen it before, where I've corrected the attribute, unchecking the box in Properties -> Advanced. Then 10 minutes later, the attribute is back.
What the heck?
Does anyone recognize this behavior or have a solution for it? Comments and thoughts are appreciated, though I already know I have sanity issues. @=) -
The archive attribute is set anytime the file is modified (Opened and read?)
For SQL, this would be understandable as the service would be running background tasks.
Anti virus?
Get File Mon from sysinternals and set a filter for that file. See who calls it.
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
-
Ah-ha! That actually makes sense. And explains why it keeps resetting everytime I look at it.
Thanks, Crispin. I'm mailing out your cookie now. @=)
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply