Comments
Sort by recent activity
Thanks, Peter...
Just what I needed! / comments
Thanks, Peter...
Just what I needed!
Sorry, posted this in the 'sticky topic'
Despite having just loaded the patch for this, I continue to get errors on backup-
SQL Backup exit code :1050
SQL error code:3202
Write on "SQLBACKUP_<string>" failed: 112(There is not enough space on the disk.)
Failed to close vdi
Needless to say, I've checked for sufficient disk space. / comments
Sorry, posted this in the 'sticky topic'
Despite having just loaded the patch for this, I continue to get errors on backup-
SQL Backup exit code :1050
SQL error code:3202
Write on "SQLBACKUP_<strin...
One addition-
I've tried the MAXTRANSFERSIZE option available, using all the prescribed sizes, from 1 mb down to 64K and I still get this issue. / comments
One addition-
I've tried the MAXTRANSFERSIZE option available, using all the prescribed sizes, from 1 mb down to 64K and I still get this issue.
Actually, acting on advice from Brian, I added the 'MAXDATABLOCK = 1048576" parameter, and all seems happy now, woithout using the MAXTRANSFERSIZE parameter.
As I recall, the file was partially created, but I'm not sure how much was written (if any) or if the file was merely created, and not written to. / comments
Actually, acting on advice from Brian, I added the 'MAXDATABLOCK = 1048576" parameter, and all seems happy now, woithout using the MAXTRANSFERSIZE parameter.
As I recall, the file was partially cre...
Pete-
I tried ALL the suggested values for MAXTRANSFERSIZE, from 1 MB down to 64 KB, and got the same result. / comments
Pete-
I tried ALL the suggested values for MAXTRANSFERSIZE, from 1 MB down to 64 KB, and got the same result.
Despite having just loaded the patch for this, I continue to get errors on backup-
SQL Backup exit code :1050
SQL error code:3202
Write on "SQLBACKUO_<string>" failed: 112(There is not enough space on the disk.)
Failed to close vdi / comments
Despite having just loaded the patch for this, I continue to get errors on backup-
SQL Backup exit code :1050
SQL error code:3202
Write on "SQLBACKUO_<string>" failed: 112(There is not enough space...
Thanks Pete !
Feel kinda dumb about not tryin' that before LOL / comments
Thanks Pete !
Feel kinda dumb about not tryin' that before LOL
Sorry, I'm not understanding this -
Are we saying that after eitehr a full DB backup and/or after a trx log backup, the trx logs are NOT truncated ?
If so this seems a pretty basic piece of functionality that SQL Backup lacks. I mean, as a DB operator, I am accustomed to log maintenance being taken care of by the backup procedure. Do we now need to create yet another job to do log cleanup ? / comments
Sorry, I'm not understanding this -
Are we saying that after eitehr a full DB backup and/or after a trx log backup, the trx logs are NOT truncated ?
If so this seems a pretty basic piece of functio...
Sure, why not ?
<chuckle>
I have a trace of the startup of the GUI as well. Would you like me to send it to you ? / comments
Sure, why not ?
<chuckle>
I have a trace of the startup of the GUI as well. Would you like me to send it to you ?
Additional 'poking' at the UI -
Under the 'Help' menu, 'Check for Updates'...
"The Update service does not recognize this product. Please contact your software vendor for updates to this produc. Error 13000" Product not registered with the Agent. / comments
Additional 'poking' at the UI -
Under the 'Help' menu, 'Check for Updates'...
"The Update service does not recognize this product. Please contact your software vendor for updates to this produc. Er...