We have a <DB Name>.sql.log which is about 30G in size.
1) We had to set to the log level to "3" to capture defragmentation info in app.log. This is probably the reason so much data is being written to the .sql.log file. Is the DB performance adversely affected due to constant writing to this file?
2) Is there way to set the max size of this file? I am trying to figure out the best way to capture sql logs without affecting DB performance