Posted by Erland Sommarskog on 04/21/07 12:43

akkha1234@gmail.com (akkha1234@gmail.com) writes:
> Our database is running in full recovery mode and we backup the log
> file every hour and the database file every night. I notice the
> timestamp of database file *.mdf remains unchanged a few days. For
> example one database has its timestamp at Apr 15 while it is Apr 20
> already.
> I am wondering if this is acceptable. How do I force the system to
> flush the data and dirty blocks to the disk more frequently? What is
> the downside to this?

I don't think you should pay any attention to the dates you see in
Explorer. The database files are open all the time, and data modifications
will not affect the dates. Only operations that affects the size of the
files does. That is, if the file autogrows, this will be refleced in
Explorer.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Re: Interesting SQL problem : How to track movement history
• Prev in forum: Re: Query Optimization
• Thread view: Re: timestamp ans status of database file

[Reply to this message]