We have a process that runs each morning to load about 40,000 rows from one server to another. In the past few weeks, the process has been having a 'log suspend' once or twice a week. This is preceded by a "log segment has fallen critically low" message.
I am a programmer and not a DBA, but our DBA has said the problem is on the programming end. But since neither the process nor the number of rows has changed, I think it's something on the database side.
The DBA said he increased the size of the transaction log a few times and that's not solving the problem.
Does anyone have any thoughts where I should start?