Comments
Sort by recent activity
Hi,
We stopped selling the Standard license at the beginning of the month, and currently only the Lite or Professional versions are available for purchase.
Saying that, existing licenses (either 5.x standard, or 4.x standard with a support contract) will continue to function in "standard" mode. The GUI will behave exactly the same as before - the licenses will not be downgraded to a Lite license by the GUI.
Hope that helps,
Jason / comments
Hi,
We stopped selling the Standard license at the beginning of the month, and currently only the Lite or Professional versions are available for purchase.
Saying that, existing licenses (either 5....
Hi,
That was the impression I was given, but the best people to ask on that would be the sales team - you can email them at sales@red-gate.com and they will be able to give you a definitive answer on what they can offer.
Hope that helps,
Jason / comments
Hi,
That was the impression I was given, but the best people to ask on that would be the sales team - you can email them at sales@red-gate.com and they will be able to give you a definitive answer ...
Hi jreynolds,
If you could drop me an email with the following information, I can investigate the issue further for you:
* The approximate date you purchased SQL Backup 4.x Standard
* The license key you are using to activate 5.x
I've just tested this myself with a 4.x Standard license, and it appears to offer me 5.x Standard (even though this is no longer on sale directly)... so if you can forward me the above information (either via PM, or to jason.cook@red-gate.com) I'll look into the issue for you.
Thanks,
Jason / comments
Hi jreynolds,
If you could drop me an email with the following information, I can investigate the issue further for you:
* The approximate date you purchased SQL Backup 4.x Standard
* The license k...
Indeed, my mistake... didn't spot that you had two "WITH" statements as well. Of course should only have a maximum of one.
Not sure what version of VB you are using, but if you are using .NET, you could use the String.Format function to try and make the code easier to understand (if you have to do this again in the future):
For example, your code would become something like:
query10 = String.Format(@ -SQL "RESTORE DATABASE {0} FROM DISK = 'G:\myFiles\CompressedBackups\{1}' WITH MOVE '{0}' TO 'G:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\{0}.mdf', MOVE '{0}_LOG' TO 'G:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\{0}.ldf', MAILTO='myemail@mydomain.com', THREADPRIORITY=6 "" -I sql -U user -P password",myString6,myFile6);
Granted it's still not ideal, but it's eliminated a significant number of the double quotes... so seems slightly less complicated. The following link may be useful (mentions C#, but should be the same in VB.net): http://blog.stevex.net/index.php/string ... in-csharp/
Hope that helps,
Jason / comments
Indeed, my mistake... didn't spot that you had two "WITH" statements as well. Of course should only have a maximum of one.
Not sure what version of VB you are using, but if you are using .NET, you...
Hi,
The generated command will not function correctly because of confusion between the various tags.
Any part of the SQL Backup command needs to go inside the -SQL "..." tag, and the -I, -U and -P tags come afterwards.
So in your example, this should be:
query10 = "-SQL ""RESTORE DATABASE " & myString6 & " FROM DISK = 'G:\myFiles\CompressedBackups\" & myFile6 & "' WITH MOVE '" & myString6 & "' TO 'G:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\" & myString6 & ".mdf', MOVE '" & myString6 & "_LOG' TO 'G:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\" & myString6 & ".ldf' WITH MAILTO='myemail@mydomain.com', THREADPRIORITY=6"" -I sql -U user -P password "
Hope that helps,
Jason / comments
Hi,
The generated command will not function correctly because of confusion between the various tags.
Any part of the SQL Backup command needs to go inside the -SQL "..." tag, and the -I, -U and -P ...
Hi,
The .dat file is the local cache of the enhanced backup history from SQL Backup, containing all the backup and restore history (minus any older data that has been purged).
The only way to reduce the file size at this stage is to purge the activity history from the enhanced backup history (the "SQL Backup data store"), using the options dialog in the SQL Backup 5 GUI.
--
As for your second question, unfortunately the variable refresh feature is not currently available in SQL Backup 5.1 (or the 5.2 patch, which only covers server components), but it is something we are considering for a future release.
Hope that helps,
Jason / comments
Hi,
The .dat file is the local cache of the enhanced backup history from SQL Backup, containing all the backup and restore history (minus any older data that has been purged).
The only way to reduc...
Hi Dinu,
For a non-default instance (in this case, the instance called "SQLSERVERE"), you need to append a "-I <instance name>" at the end... so your command would become:
"c:\program files\red gate\sql backup\sqlservere\SQLBackupC.exe" -SQL "BACKUP DATABASE IRISmaster_new TO DISK = 'e:\temp\IRISmaster.sqb' WITH PASSWORD = '...'" -I SQLSERVERE
Hope that helps,
Jason / comments
Hi Dinu,
For a non-default instance (in this case, the instance called "SQLSERVERE"), you need to append a "-I <instance name>" at the end... so your command would become:
"c:\program files\red gat...
The following link may help to answer your questions: http://msdn2.microsoft.com/en-us/library/ms190203.aspx
The log shipping should continue unaffected, since you are still generating logs, and have not broken the log chain. The one major thing to note from the article is to perform a log backup directly before, and directly after, the change to/from bulk-logged mode to minimise any potential loss if a server failure was to occur during that period.
Hope that helps,
Jason / comments
The following link may help to answer your questions:http://msdn2.microsoft.com/en-us/library/ms190203.aspx
The log shipping should continue unaffected, since you are still generating logs, and hav...
Hi,
The reason you will get that message is because SQL Backup is unable to access or create the location in question. For UNC locations, the share must already exist, and the SQL Backup Agent account requires sufficient permissions to access and write to it.
You can run the following command, which will check what permissions the SQL Backup Agent has to the folder... execute master..sqbutility 999, 'RWE', '\\testsrv\backup'
If this is successful and the agent has read (R), write (W) and execute (E) permissions, it will return: <SQBUTILITYRESULT>:1:
If there is a problem, the 1 will be replaced by a 0, and a message will be added at the end, for example: <SQBUTILITYRESULT>:0:Folder does not exist : \\jason\temp2\
Hope that helps,
Jason / comments
Hi,
The reason you will get that message is because SQL Backup is unable to access or create the location in question. For UNC locations, the share must already exist, and the SQL Backup Agent acc...
Hi,
I've looked for the section in the help you are referring to, and it does seem to be slightly ambiguous:
"During the backup process, if any of the files cannot be written a warning is raised. However, the backup process continues as long as at least one specified backup file can be written. If none of the files can be written, an error is raised and the backup process is stopped."
What this should mean, is that once the actual backing up phase has begun, a subset of the files can fail and the rest should continue. However, if a pre-backup phase failure occurs (for example, the missing directory), the backup task will error out before the backing up phase begins.
Depending on your needs, the COPYTO keyword may be able to help. The difference with COPYTO is that the primary server's backup is done first, and *then* copied to the secondary server. If for any reason the secondary server is unavailable, the backup will succeed with a warning, rather than fail.
The main downside to the COPYTO is that you only have one copy of the file available until the COPYTO completes, compared to 2 or more when the original backup completes.
I'll also pass this on to our developers and they may be able to improve the situation in a future release.
Hope that helps,
Jason / comments
Hi,
I've looked for the section in the help you are referring to, and it does seem to be slightly ambiguous:
"During the backup process, if any of the files cannot be written a warning is raised. H...