Comments
Sort by recent activity
It was the deletion of the application log files that was causing the slowdown. These files were in the folder C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\(LOCAL)Since we do transaction log backups every 5 minutes on two databases, and the file purge was set to 90 days, the application log folder had over 46,000 files. I manually purged the folder and set the option in SQL backup to only keep 2 days worth of logs.
Just an FYI, I was somewhat confused by the reference to "log files from log folder" reference in the above post. At first I thought log files referred to transaction logs. Even when I looked in the Options window in the GUI, I thought the reference to the log file folder was for transaction logs. After a few ..umm...minutes :oops:, I finally realized that the application was logging its activity to this folder. So my suggestion is to be a little more explicit when referring to a "log".
Thanks,
John / comments
It was the deletion of the application log files that was causing the slowdown. These files were in the folder C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\(LOCAL)Si...
I am using UNC paths for flexibility since the script is built dynamically. I will hardcode the local drive information and see if it happens again.
Thanks,
John / comments
I am using UNC paths for flexibility since the script is built dynamically. I will hardcode the local drive information and see if it happens again.
Thanks,
John
Has there been any further insight as to what causes this? What are the performance implications setting a different MAXDATABLOCK size? I have found that I can go to a maximum of 3407872 before it breaks, but I didn't see any performance difference at lower values. / comments
Has there been any further insight as to what causes this? What are the performance implications setting a different MAXDATABLOCK size? I have found that I can go to a maximum of 3407872 before it ...