Comments
Sort by recent activity
Deepak,
I suggest you contact our support department (support@red-gate.com) as they deal with any requests for Hotfixes etc and may well be able to provide you with the probable time frames for 5.2 etc.
Regards,
- James / comments
Deepak,
I suggest you contact our support department (support@red-gate.com) as they deal with any requests for Hotfixes etc and may well be able to provide you with the probable time frames for 5.2...
Hi,
There was an error in our generation of log shipping scripts for case sensitive servers, this will be fixed for 5.2.
Unfortunately the only work around at this point is to set up log shipping by hand - this can be done via the following:
Back up the source database and set the copy to parameter to your network share, then restore this backup to the destination server leaving the database in NO RECOVERY or STANDBY and move the backup to the destination directory on the target server.
Next set up a transaction log backup job with the copy to target as the network share.
Finally create a restore job with a script similar to:
master..sqlbackup '-SQL "RESTORE LOGS [destinationDatabaseName] FROM DISK = ''\\server\share\directory\*.sqb'' WITH MOVE TO = ''c:\destination directory'', STANDBY|NORECOVERY, ...."'
and schedule it to run a few minutes after the backup job with the same frequency.
Sorry you have to do this by hand but the issue will be fixed as soon as 5.2 is released.
Any problems please let us know or get in contact with our support department - support@red-gate.com.
Regards,
- James / comments
Hi,
There was an error in our generation of log shipping scripts for case sensitive servers, this will be fixed for 5.2.
Unfortunately the only work around at this point is to set up log shipping b...
Carl,
Using a telnet client to test SMTP is a good test form our point of view as it makes a direct TCP connection rather than using any windows subsystems (other than the TCP stack). Directions on how to do it are describe here: http://www.rdpslides.com/webresources/FAQ00035.htm
Hope this helps,
- James / comments
Carl,
Using a telnet client to test SMTP is a good test form our point of view as it makes a direct TCP connection rather than using any windows subsystems (other than the TCP stack). Directions on...
Hi there,
Can you try closing SQL Backup and then deleteing the files in
C:\Documents and Settings\<user name>\Local Settings\Application Data\Red Gate\SQL Backup\Server Data
Thanks,
- James / comments
Hi there,
Can you try closing SQL Backup and then deleteing the files in
C:\Documents and Settings\<user name>\Local Settings\Application Data\Red Gate\SQL Backup\Server Data
Thanks,
- James
John,
Probably a little late for you now but RESTORE HEADERONLY works with SQL Backup as well.
master..sqlbackup '-SQL "RESTORE HEADERONLY ..."'
- James / comments
John,
Probably a little late for you now but RESTORE HEADERONLY works with SQL Backup as well.
master..sqlbackup '-SQL "RESTORE HEADERONLY ..."'
- James
Hi Thomas,
Sorry you have hit this problem - please see this post here for a resolution: http://www.red-gate.com/messageboard/vi ... php?t=4779 The issue will be fixed in 5.1
- James / comments
Hi Thomas,
Sorry you have hit this problem - please see this post here for a resolution: http://www.red-gate.com/messageboard/vi ... php?t=4779 The issue will be fixed in 5.1
- James
You probably wont be able to put the databases in STANDBY to start with as SQL Server does not support RESTORE .. STANDBY and an upgrade but afterwards you can do it with NO RECOVERY.
I've never tried doing a full RESTORE with NO RECOVERY followed by a RESTORE WITH STANDBY followed by RESTORE LOG with STANDBY - this might be one way of setting up log shipping doing an upgrade with standby.
- James / comments
You probably wont be able to put the databases in STANDBY to start with as SQL Server does not support RESTORE .. STANDBY and an upgrade but afterwards you can do it with NO RECOVERY.
I've never tr...
At this time it is not possible to control how much history the UI caches other than changing what is on the server. If people are finding this is causing them problems - other than on inital server registration - then please let me know and we will have a look into what we can do.
- James / comments
At this time it is not possible to control how much history the UI caches other than changing what is on the server. If people are finding this is causing them problems - other than on inital serve...
Hi,
The SQL Backup UI tries to detect SQL Backup jobs, parse them and figure out which jobs are backup jobs and which are not, when they are going to run, which database they affect and how long each run of the job will run.
After your changes the UI is no longer picking up your job as a SQL Backup job.
In this case its probably because you have multiple steps - for this case we had a long discussion on how to deal with editing and displaying these sorts of jobs and decided initially that it was best to deal with them in the most simple way which was not to support it - Our thought process was we wanted to spend our time working on making the Timeline and job editing/creation as good as possible rather than spending time on writing a more generic job editing UI. There is another issue with multi step jobs which is trying to predict how long the steps before the backup step will run for so we can show them accurately on the timeline.
It would not be that difficult to change the UI's logic so that if a job has multiple steps and just one of those performs a backup we could allow editing of that step via the UI - I'm not sure what we will do for the timeline but we will have a good think [image] . If enough people want it we will have a serious look at it for 5.1.
Just for reference the following things will definately stop the UI picking up on SQL Backup jobs
- Multiple steps in the job (let me know if this causes you problems)
- Use of Dynamic SQL
- Use of Dynamic SQL Backup statements
- Use of stored procedures which wrap the SQL Backup call
- James / comments
Hi,
The SQL Backup UI tries to detect SQL Backup jobs, parse them and figure out which jobs are backup jobs and which are not, when they are going to run, which database they affect and how long ea...
Martin,
This can happen under some circumstances and it does not affect the actual trail just the reporting of it in the UI only, it was somthing we spotted during final testing before release and decided it was not worth delaying the release for or risk fixing at the last minute.
You should have a 14 day trial - if you have any problems with your actual trail then please let us know and we will sort out a trial extension for you.
Regards.
- James / comments
Martin,
This can happen under some circumstances and it does not affect the actual trail just the reporting of it in the UI only, it was somthing we spotted during final testing before release and ...