I am having an issue with out of control transaction logs. Here's the scenario:
We have a SQL based application. We use 2 database servers, one for production, and a second one for test/training. Upon request, we refresh the test databases (App_462, App_463) with backups from the production databases (App_262, App_263).
Once the main restore has been completed, we have to run a SQL Agent job on each database on the test server "Change from 262 to 462" and "Change from 263 to 463". When running the jobs, one at a time, the transaction logs for the database grow to the point of filling up the data drive on the test server.
The databases are about 30GB each, and the transaction logs start at about 100MB. While the jobs run, the translogs grow to over 160GB.
Is there any way to curb the transaction logs, shut them off, or rein them in while running these 2 jobs? Do I need to alter the jobs so they run more efficiently? I, currently, cannot complete the refresh because the drive is filling up and the jobs fail. I can provide the SQL code if needed.