User profile for abuttery

I set the DefaultData and DefaultLog values in the registry as "E:" and "F:" respectively. SQL Backup 5.3.0.178 uses the DefaultData directory but appears to ignore the DefaultLog directory when restoring to a new database. / comments

I set the DefaultData and DefaultLog values in the registry as "E:" and "F:" respectively. SQL Backup 5.3.0.178 uses the DefaultData directory but appears to ignore the DefaultLog directory when r...

0 votes

Thank you for referring me to this. I will check it out as soon as I get some time and let you know how it goes. / comments

Thank you for referring me to this. I will check it out as soon as I get some time and let you know how it goes.

0 votes

In my environment that is not a problem. The tables that I'm concerned with are in a data warehouse that is updated each morning by a defined process. The backups occur each evening after business hours. The users only have read-only access (db_datareader) to the database as a whole. Only the DBA staff and the nightly processing jobs have the appropriate permissions to update the data in the Warehouse. / comments

In my environment that is not a problem. The tables that I'm concerned with are in a data warehouse that is updated each morning by a defined process. The backups occur each evening after busines...

0 votes

Thanks. I have the toolbelt which includes those products so I'll take a look at them. I'd still prefer to have the object level restore capability in SQL Backup but having it available in another tool will suffice for now. / comments

Thanks. I have the toolbelt which includes those products so I'll take a look at them. I'd still prefer to have the object level restore capability in SQL Backup but having it available in anothe...

0 votes

I just installed SQL Backup 5.2 and then upgraded the server side components and the email password issue is now fixed. Thanks Red-Gate for fixing this so quickly. / comments

I just installed SQL Backup 5.2 and then upgraded the server side components and the email password issue is now fixed. Thanks Red-Gate for fixing this so quickly.

0 votes

I originally had this issue with SQL Backup v5.0 so I upgraded to 5.1 to see if it fixed the problem; after that did not fix the problem I searched the forums to see if anyone else was having the problem and found one of the posts about where to look in the registry. Once I found the registry keys I was able to open them on the server that was not working and a server that was working and noticed that the encrypted/encoded passwords were different even though I knew they were both correct. That's when I decided to copy the registry key value from the working server and paste it into the registry on the server that was not working which resolved the issue. / comments

I originally had this issue with SQL Backup v5.0 so I upgraded to 5.1 to see if it fixed the problem; after that did not fix the problem I searched the forums to see if anyone else was having the p...

0 votes

I was able to get the email working by copying the password from the registry on another server into the registry on the server that was not working properly. It appears that the first character of the password was incorrectly encrypted. / comments

I was able to get the email working by copying the password from the registry on another server into the registry on the server that was not working properly. It appears that the first character o...

0 votes

Thanks. This is what I needed. / comments

Thanks. This is what I needed.

0 votes

No. Here is the stored procedure I'm running though: CREATE procedure dbo.backupSchemasSQLBackup as declare @schemaName varchar(50) declare @sql varchar(4000) /* Make sure database is online (status & 512) = 0 before trying to back it up. */ declare schemaList cursor read_only for select [name] from master..sysdatabases where [name] not in ('tempdb') and (status & 512) = 0 order by [name] open schemaList fetch next from schemaList into @schemaName while ( @@fetch_status = 0 ) begin -- Delete Old Database Backup set @sql = 'exec xp_cmdshell ''del L:\SQL_Backups\' + @schemaname + '.sqb''' print @sql exec ( @sql ) -- Backup Database to New SQL Backup File (the one just deleted) set @sql = 'master..sqlbackup ''-SQL "BACKUP DATABASE [' + @schemaName + '] TO DISK = ''''L:\SQL_Backups\' + @schemaName + '.sqb'''' WITH NAME = ''''Database (' + @schemaName + '), ' + replace(replace(replace(convert(varchar(19),getdate(),121),'-',''),':',''),' ','_') + ''''', DESCRIPTION = ''''Backup on ' + convert(varchar(19),getdate(),121) + ' Database: ' + @schemaName + ' Server: NJCINNT37'''', INIT, MAILTO = ''''abuttery@impactrx.com'''', COMPRESSION = 1"''' print @sql exec ( @sql ) -- Copy ZIP File to NT34 set @sql = 'exec xp_cmdshell "copy L:\SQL_Backups\' + @schemaname + '.sqb ' + '\\NJCINNT34\f$\NT37\' + @schemaname + '.sqb", no_output' print @sql exec ( @sql ) print '----------------------------------------------------------------------' fetch next from schemaList into @schemaName end close schemaList deallocate schemaList GO The backups are being run on NJCINNT37 and then a copy of the backed up file is saved on NJCINNT34 for quick disaster recovery. The basic question still remains, why is SQL Backup indicating that the backup was successful when it cannot even write to the output device? -- Alex Buttery / comments

No. Here is the stored procedure I'm running though:CREATE procedure dbo.backupSchemasSQLBackup as declare @schemaName varchar(50) declare @sql varchar(4000) /* Make sure dat...

0 votes

I will have databases on SQL 2000 for the foreseeable future and would like SQL 2000 capability / comments

I will have databases on SQL 2000 for the foreseeable future and would like SQL 2000 capability

0 votes

How can we help you today?

abuttery

Comments