Comments
Sort by recent activity
There isn't a way to restore all backup sets. You would need to create separate restore jobs for each database.
/ comments
There isn't a way to restore all backup sets. You would need to create separate restore jobs for each database.
Could you please run some tests for me using the SQL Backup Test Utility? You can download the test utility from here.
Select the 'Tools > Misc tests' item from the main menu, enter the path to the folder where you copied the backup file to, and click on the 'Process button'. What is the reported disk sector size? / comments
Could you please run some tests for me using the SQL Backup Test Utility? You can download the test utility from here.
Select the 'Tools > Misc tests' item from the main menu, enter the path to the...
During a restore, SQL Server needs to create and size the data and log files. If instant initialization is active, it won't need to zero-ise the data files. Please see https://msdn.microsoft.com/en-us/librar ... 2147217396 for further details. / comments
During a restore, SQL Server needs to create and size the data and log files. If instant initialization is active, it won't need to zero-ise the data files. Please see https://msdn.microsoft.com/...
Could you please post the contents of the SQL Backup log for the backup process that reported those numbers? The default folder where the logs are stored is C:ProgramDataRed GateSQL BackupLog<instance name>, unless you're using Windows 2003 or older OSs, for which the default folder is then 'C:Documents and SettingsAll UsersApplication DataRed GateSQL BackupLog<instance name>'. / comments
Could you please post the contents of the SQL Backup log for the backup process that reported those numbers? The default folder where the logs are stored is C:ProgramDataRed GateSQL BackupLog<inst...
Activations are machine-specific, so if you created the activation requests from the same machine (i.e. the machine ID value is identical in both attempts), it only counts as a single activation. / comments
Activations are machine-specific, so if you created the activation requests from the same machine (i.e. the machine ID value is identical in both attempts), it only counts as a single activation.
Could you please run the following in Management Studio when connected to the instance and post the results for @mode and @version? Also, does @serial return the correct serial number? DECLARE @mode INT
DECLARE @version varchar(128)
DECLARE @serial varchar(128)
EXEC master..sqbutility 1021, @mode OUTPUT, @version OUTPUT, @serial OUTPUT
SELECT @mode, @version, @serial
/ comments
Could you please run the following in Management Studio when connected to the instance and post the results for @mode and @version? Also, does @serial return the correct serial number?DECLARE @mod...
Encrypted data don't compress very well. Try taking a native SQL Server backup of your TDE database, then compress the backup file using Winzip or another compression tool. SQL Backup's compression level ought to be near those levels. / comments
Encrypted data don't compress very well. Try taking a native SQL Server backup of your TDE database, then compress the backup file using Winzip or another compression tool. SQL Backup's compressi...
Was the database in use when you tried to restore the log? When you performed the restore, SQL Backup waited for 30 seconds for SQL Server to respond to the backup request, but SQL Server did not respond. Try running the restore again, but this time, in that 30-second interval, run sp_who2 to see if anyone is connected to the database.
Another option is to use the DISCONNECT_EXISTING option in SQL Backup, so that it attempts to close all connections prior to running the restore e.g. EXEC master..sqlbackup '-sql "RESTORE LOG ... WITH NORECOVERY, DISCONNECT_EXISTING"'
/ comments
Was the database in use when you tried to restore the log? When you performed the restore, SQL Backup waited for 30 seconds for SQL Server to respond to the backup request, but SQL Server did not ...
There is no password set for the local database file. SSMS 2014 onwards do not support SQL Server Compact.
Another option to access the tables is via the sqbdata extended stored procedure e.g. in SSMS when connected to your SQL Server instance:
EXEC master..sqbdata 'SELECT * FROM backuphistory'
The tables are:
backuphistory
backuplog
backupfiles
backupfiles_copylist
backupfiles_copylist_log
restorehistory
restorelog
restorefiles
/ comments
There is no password set for the local database file. SSMS 2014 onwards do not support SQL Server Compact.
Another option to access the tables is via the sqbdata extended stored procedure e.g. in ...
SQL Backup uses the AES (Rjindael) algorithm for encryption purposes. 256-bit keys are more secure, but eats up more CPU cycles compared to 128-bit keys. The difference might be nominal, depending on your setup. / comments
SQL Backup uses the AES (Rjindael) algorithm for encryption purposes. 256-bit keys are more secure, but eats up more CPU cycles compared to 128-bit keys. The difference might be nominal, dependin...