I believe a DBA need to have an approval for performing recycle error log operation on production server, am i right? and we create another new error log by keeping the older error log files in order to preserve that information contained in those older error logs or is there any specific reason to create new one while keeping the older error logs ? How often is it good to recycle the error log,only when we ran out of disk?
Cycling the error log isn't related to running out of disk (if error log size is causing a problem with disk space, you likely have much larger issues than how often to cycle the error log). Create a job to cycle the error log every day at midnight. This keeps the files small-ish so they load quickly when you need to review or query them. I'm sure there could be some discussion as to how often to cycle them (daily/weekly/monthly/never), but daily keeps things nicely organized with the trade-off being limited to just over 3 months worth of log data in the files. Keep at least one month worth of files since you might have to go back several weeks to see when something began occurring. 99 is the highest number of log you can keep and there is no real downside to keeping that many.