The log file for my SQL Server 2014 database is growing rapidly (currently in 32 GB in COMPLETE RECOVERY mode). This is creating storage issues on my server.
The database has a set of job's with large
SELECT - UPDATE - DELETE from another DB occurring at different times of the day.
- How do I avoid rapid growth of the log file?
- What practices should I use to minimize log growth?
COMMIT TRANSACTIONis generally not used in
STORE PROCEDURES, is it essential to add them as part of improvement?
- Researching I read that I should use TRUNCATE TABLE, WITH (NOLOCK) as part of optimization, I would like to know your opinions.
Sorry for my English, thank you for your support.