NTFS transaction log disable

can the NTFS recovery transaction log be disabled...
and if not is there a way to increase the log space
bilutherAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TMSCommented:
These are different things. NTFS has a feature that ensures complete update to files. This add safety to the NTFS file system, as it is less likely to corrupt the file system (file allocation, bitmap and NTFS structures scattered all around an NTFS partition)
The NTFS file system takes great care to write and record changes as they are made to the disk, so it is possible to restart in a 'known' state when the system restarts and tries to 'recover'...
Truncate log on check point is a SQL server option that allows the syslog table to be truncated (read: lost) when SQL server checkpoints.
Abstract from the SQL server books online...
The checkpoint mechanism is an automatic means for guaranteeing that completed transactions are regularly written from SQL Server's own disk cache to the database device. A checkpoint writes all dirty pages cached pages that have been modified since the last checkpoint to the database device.


0
bilutherAuthor Commented:
Edited text of question
0
z1Commented:
Sorry answer to both questions in NO as far as I know. Answer to the 1st one is NOT FOR SURE - it's first and basic fs feature, if you need one which never writes, go on...
Are you writing LARGE files using NT compression? Comment only if so, I'll go on.
z1
0
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

tbaffyCommented:
The NTFS logfile ($logfile) can range in size from 4 MB to 10 MB and is circularly reusable.  What this means is that the transaction entries in the log file wrap around back to the beginning of the file when the file reaches maximum size.  There is little point in making this file larger when it automatically recycles its own space.

Tom
0
BlackManCommented:
To add on tbaffy's comment, it is correct that the logfile i circulary reusable. The Log File Service (LFS) sees it as an infinitely large file, but if it should happe to run full, LFS halts I/O activity, that means, blocking for creation and deletion of files. Then it complete waiting transactions, calls the cache manager to flush unwritten data, and then continues to process I/O's.
Under normal circumstances, you will never notice this, as it has no effect on executing programs.
If you use a FAT volume, there is no transaction logging..
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bilutherAuthor Commented:
suggestion of using FAT is helpful...

0
eliuhaCommented:
the punched card does not have a transaction logging as well
http://en.wikipedia.org/wiki/Punched_card

what are you trying to do ? or in other words, why don't you like the log ?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.