Comments
Sort by recent activity
Add a new SQL Server, then use SERVERNAME\INSTANCE,PORT to connect. You can then change the alias to just display the server name if you want your list to look clean. / comments
Add a new SQL Server, then use SERVERNAME\INSTANCE,PORT to connect. You can then change the alias to just display the server name if you want your list to look clean.
Mindflux wrote:
petey wrote:
Yes.
Perfect. This morning's backup went flawless and all the older data has been erased.
Have you attempted to edit that backup job with the SQLBackup GUI after you added those options? / comments
Mindflux wrote:
petey wrote:
Yes.
Perfect. This morning's backup went flawless and all the older data has been erased.
Have you attempted to edit that backup job with the SQLBackup GUI af...
laurencerooks wrote:
Son of a gun. Thanks cgriffin. I think I know why we're having our issues on certain servers and not on others.
Laurence
Is it because you've used the GUI exclusively on some and not on the others? / comments
laurencerooks wrote:
Son of a gun. Thanks cgriffin. I think I know why we're having our issues on certain servers and not on others.
Laurence
Is it because you've used the GUI exclusively on...
Laurence, I'm not able to edit the SQL2005 job on the server on which the GUI is installed. According to Dan Archer, it has to do with the way SQLBackup treats jobs that are edited by something other than the GUI. / comments
Laurence, I'm not able to edit the SQL2005 job on the server on which the GUI is installed. According to Dan Archer, it has to do with the way SQLBackup treats jobs that are edited by something ot...
I understand completely about the integrity of the job, but the problem is, even after I put the job back the way it was originally established, the GUI still can't edit.
I don't recall seeing any kind of 'heads-up' about this situation when researching the available options not supported by the GUI. It's almost as if we were being told to go ahead and use all these great options while not being told about the editing problem. In an environment where a single SQL administrator goes on vacation or quits his/her job, someone with less SQL knowledge needs the GUI to work. That speaks to the quality of SQL Backup's GUI. I don't want anyone but a SQL admin messing directly with SQL scripts in the SQL agent on my systems.
As for future options, I'll add my vote to be able to manage backup copies, and being able to independently set ERASEFILES to different amounts. / comments
I understand completely about the integrity of the job, but the problem is, even after I put the job back the way it was originally established, the GUI still can't edit.
I don't recall seeing any ...
And thanks for the support replies. I'm not ready to deploy 5.1 to any more servers until the bugs are worked out, but I'm not getting rid of it either. Still a good product. / comments
And thanks for the support replies. I'm not ready to deploy 5.1 to any more servers until the bugs are worked out, but I'm not getting rid of it either. Still a good product.
That's kinda what I figured, but I didn't see any other way to add that 'fileoptions' and the documentation says we can use it. / comments
That's kinda what I figured, but I didn't see any other way to add that 'fileoptions' and the documentation says we can use it.
'Cannot edit command' window pops up with the message 'The GUI does not support editing the command you selected'. Still can't edit any existing jobs. Any help is appreciated. / comments
'Cannot edit command' window pops up with the message 'The GUI does not support editing the command you selected'. Still can't edit any existing jobs. Any help is appreciated.
I'm having trouble editing ANY jobs this morning. The only thing I did differently yesterday was to manually edit my step scripts via Enterprise Manager/Management Studio because the SQLBackup GUI doesn't allow you to set a delete files timeframe for the 'copy to network' option. I have removed the code I added on a couple of jobs but it still won't let me edit. Sounds like a permissions thing but I haven't figured it out yet. / comments
I'm having trouble editing ANY jobs this morning. The only thing I did differently yesterday was to manually edit my step scripts via Enterprise Manager/Management Studio because the SQLBackup GUI...