Why are the last update dates of SQL Server data files and log files inaccurate?

Someone asked why SQL server data has changed, but why is the best modification date of database files and log files not changed. In fact, this is a normal behavior. The modification date of the SQLServer file is in SQLSer

Someone asked why SQL server data has changed, but why is the best modification date of database files and log files not changed. In fact, this is a normal behavior. The modification date of the SQLServer file is in SQLSer

Someone asked why SQL Server data has changed, but why is the best modification date of database files and log files not changed. In fact, this is a normal behavior.

The modification date of the SQL Server File is when the SQL Server closes the file (Shutdown or the database is Detach, Offline) or the SQL Server data file or log file increases (automatic or manual growth, these are all tested by myself ). In other cases, SQL Server directly updates data and website space without bypassing the file system, so it does not update Modify date.

From the performance perspective, if SQL Server updates the file Modify date every time, the overhead is very large for a large OLTP transaction database in seconds.

In addition, database users are concerned with data changes, which are queried from the database application software, rather than through the WINDOWS file system. In addition, after the database is started, only SQL Server can exclusively update data files and log files, so there is no other software update, so the last file update time is not very important.

This article is from the "follow SQL Server Technology" blog, Hong Kong virtual host, please be sure to keep this source

, US space