We have a 3rd party system that makes heavy use of SQL. Its going 24/7, polling for records to process. The interface to SQL is a set of procedures and/or inline statements defined (that my team has written) within various points in the 3rd party
system. Im trying to figure out what would be causing the transaction log to get written to as much as it is. So im running a trace in an attempt to watch activity off-hours when no users are on the system. Im using the built in "tuning"
template and including a few other columns such as rowcount and writes.
Am I correct to assume that any operation that is doing an update or insert, even to a temp table, is going to write to the log? Also, can the amount of space referenced in the "writes" column of the profiler window will be roughly the same amount of space consumed in the log? That meaning each write = 8K page X number of writes?
About the same time I started the profiler trace, I got a snapshot of the space in the db and log. Then kept an eye on it. Sure enough, something is writing to the tlog. Its something like 5 mb / min, which seems excessive for a time when there should be no records to process and no users are on the system giving it new records to process. Ive got the textdata column in the profiler trace and will probably start to research those statements a bit, especially the stored procedures being called which introduce writes yet should not be updating anything, at least not at the times its running.
Am I correct to assume that any operation that is doing an update or insert, even to a temp table, is going to write to the log? Also, can the amount of space referenced in the "writes" column of the profiler window will be roughly the same amount of space consumed in the log? That meaning each write = 8K page X number of writes?
About the same time I started the profiler trace, I got a snapshot of the space in the db and log. Then kept an eye on it. Sure enough, something is writing to the tlog. Its something like 5 mb / min, which seems excessive for a time when there should be no records to process and no users are on the system giving it new records to process. Ive got the textdata column in the profiler trace and will probably start to research those statements a bit, especially the stored procedures being called which introduce writes yet should not be updating anything, at least not at the times its running.