Comments
Sort by recent activity
If you're absolutely nuts, you could dynamically generate random passwords for each backup and save them to password table. This way any backup can be released without compromising the others.
Restore scripts would naturally need to perform a lookup to the password table. / comments
If you're absolutely nuts, you could dynamically generate random passwords for each backup and save them to password table. This way any backup can be released without compromising the others.
Rest...
Hi Mike,
So what you'd like is a 'time elapsed' metric displayed in SQL Data Generator so you can use the product as a benchmarking tool?
You probably know this already but just in case I thought I'd mention that disk access on VMs is massively degraded if you use a virtual disk instead of mapping a physical disk directly. That'll be the biggest impact on disk performance.
I'm not sure if SDG would be the best tool to use for benchmarking as it only performs inserts. Is it strictly disk performance that you're interested in?
Regards, / comments
Hi Mike,
So what you'd like is a 'time elapsed' metric displayed in SQL Data Generator so you can use the product as a benchmarking tool?
You probably know this already but just in case I thought I...
Hi Richard,
Currently SQL OLR isn't optimized for large databases, which explains in part the reduced performance you're experiencing. The type of compression used and disk speed can also affect the time taken to parse a backup file for objects.
To address the needs of customers in your position we have been developing a novel approach to object recovery, to be released in a few months.
Regards, / comments
Hi Richard,
Currently SQL OLR isn't optimized for large databases, which explains in part the reduced performance you're experiencing. The type of compression used and disk speed can also affect th...
Hi David,
Email settings are stored in the registry of the machine hosting the sql instance. However, in the latest release of v6 the registry keys are in a new location (on 64-bit machines). Please check that the user account that SQL Backup uses has permissions in HKLM/Software/Redgate/.
You should see keys such as: HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\(LOCAL) with values like 'SMTPUserName' (Where (LOCAL) is the instance name).
Regards, / comments
Hi David,
Email settings are stored in the registry of the machine hosting the sql instance. However, in the latest release of v6 the registry keys are in a new location (on 64-bit machines). Pleas...
Hi David,
SQL Backup 6 uses a different file format, which is why your seeing this error. You can, however, convert a version 6 backup to a version 5 backup using SQBConverter.exe (commandline) or SQBConverterGUI.exe.
You'll find these programs in the SQL Backup installation directory. Note that these converters also allow you to convert backups to native standard SQL Server backups, so you must use the right parameter / check the checkbox to make sure you'll generating a v5 file, rather than a .bak backup.
Regards, / comments
Hi David,
SQL Backup 6 uses a different file format, which is why your seeing this error. You can, however, convert a version 6 backup to a version 5 backup using SQBConverter.exe (commandline) or ...
Hi mrclod,
It's possible that you're experiencing a compatibility issue that has been fixed in the later versions. Please upgrade to version 6.4 and try again (from the UI, you can click 'check for updates'). You may also be interested in trying SQBConverter.exe (found in the UI installation directory) which serves the same purpose as sqb2mtf.
Regards, / comments
Hi mrclod,
It's possible that you're experiencing a compatibility issue that has been fixed in the later versions. Please upgrade to version 6.4 and try again (from the UI, you can click 'check for...
Hi rgiesbrecht,
That's a sensible suggestion. I've logged your request (item number SB-4528) and it will be reviewed for the next release.
Thanks, / comments
Hi rgiesbrecht,
That's a sensible suggestion. I've logged your request (item number SB-4528) and it will be reviewed for the next release.
Thanks,
Also, in the UI, if you select another server and then go back to the first one you will force a refresh of the in progress information. It's just as accurate as sqbstatus 1 (that's what it uses) but doesn't update that frequently.
Regards, / comments
Also, in the UI, if you select another server and then go back to the first one you will force a refresh of the in progress information. It's just as accurate as sqbstatus 1 (that's what it uses) b...
Yes, this supported. SQL Backup's syntax for this is similar to T-SQL's. exec sqlbackup '-SQL "BACKUP DATABASE [MyDB] TO DISK = ''e:\backups\r.sqb'' WITH COMPRESSION = 4, INIT, THREADCOUNT = 3"'
--
exec sqlbackup '-SQL "RESTORE DATABASE [MyDB] FILEGROUP=''secondary'' FROM DISK = ''e:\backups\r.sqb'' WITH NORECOVERY"'
exec sqlbackup '-SQL "BACKUP LOG [MyDB] TO DISK = ''e:\backups\tail.sqb'' WITH COPY_ONLY, INIT"'
exec sqlbackup '-SQL "RESTORE LOG [MyDB] FROM DISK = ''e:\backups\tail.sqb'' WITH RECOVERY"'
/ comments
Yes, this supported. SQL Backup's syntax for this is similar to T-SQL's.exec sqlbackup '-SQL "BACKUP DATABASE [MyDB] TO DISK = ''e:\backups\r.sqb'' WITH COMPRESSION = 4, INIT, THREADCOUNT =...
Yes, the move to the main branch of the registry was intentional. This was to address an issue with registry key replication on Windows Server 2003 x64 based clusters. The documentation will shortly be updated.
Cheers, / comments
Yes, the move to the main branch of the registry was intentional. This was to address an issue with registry key replication on Windows Server 2003 x64 based clusters. The documentation will shortl...