I'm a little confused about the simple recovery model after reviewing our log-files and their sizes, and especially the file timestamp.
I'm truncating all tables in a database every day and fill them up again using BULK INSERT and INSERT...SELECT. Doesn't this hit the transaction log *at all*?? The "date modified" timestamp in windows explorer is set to 20th of november even though the db is truncated and filled up every single day. Or does this simply mean that the file is beeing used but the free space is suficcient for all the operations beeing done, hence there is no need to change the actual file?
-- Lumbago "Real programmers don't document, if it was hard to write it should be hard to understand"
"The "date modified" timestamp in windows explorer is set to 20th of november "
That will be the last re-start of SQL Server, or the last extension of the table - whichever is newer.
Just writing to the file doesn't adjust the timestamp - until SQL Server is shut down.
I expect this has to do with the exclusive lock that SQL Server places on the file - which in turn is probably an efficiency thing so that Windows doens;t have to tickle the Timestamp in the Directory EVERY time each write occurs!