Comments
Sort by recent activity
I know; how about I open my eyes and actually look at the screen *groan*
Sorry guys, I have found the option in the drop down to split into multiple files.
:oops:
Cheers / comments
I know; how about I open my eyes and actually look at the screen *groan*
Sorry guys, I have found the option in the drop down to split into multiple files.
:oops:
Cheers
Great! Thanks for that. I have applied the upgrade to 5.3 and things appear to be running now.
So I just need to schedule in a recycle of the SQL service after adding the -g switch and the world will hopefully be a happy place *hopefully*
Thanks again for both of your help/clarification on this issue. / comments
Great! Thanks for that. I have applied the upgrade to 5.3 and things appear to be running now.
So I just need to schedule in a recycle of the SQL service after adding the -g switch and the world wi...
Thanks Chris and Petey
I will look into upgrading to 5.3; as I mentioned the log file is being generated - does this mean that the files that are generated are not in fact valid?
And why is it that my backup never fails but the log backup generally does?! I would have expected both to fail under these circumstances?
This may not be the best place to pose this question but is there an easy way to identify the usage of memory that SQL is using, to identify when this is getting low? Some system view or something?
What I am thinking I would like to specifically identify (other than waiting for the error logs from SQLBackup) the current memory available and then add the -g switch to increase the 'memtoleave' and then monitor it going forward.
Any help in this front?
Thanks again for the assistance.
Regards
Troy / comments
Thanks Chris and Petey
I will look into upgrading to 5.3; as I mentioned the log file is being generated - does this mean that the files that are generated are not in fact valid?
And why is it that...