SQL Server Performance

db archiving filling up logs and physical drive

Discussion in 'General DBA Questions' started by v1rtu0s1ty, Aug 12, 2005.

  1. v1rtu0s1ty New Member

    hey guys,

    What could be your hunch about a code issue on our vendors sql archive program wherein it uses up all the space in the physical drive? We are aware that our dba configured the log to use all the space in that drive. Is it because of the number of commits such as "do commit if it reaches 100000"? If so, am I correct that doing multiple commits such as in every 10,000 will help in not eating up more space?

    Thanks,

    v1rt

Share This Page