Comments
Sort by recent activity
Hello,
Can you verify this license agreement. Because when we purchased our 25 licenses we were told that it was per SQL instance regardless of if on the same server virtual or physical in fact when we installed Red-Gate it needed to be registered on each instance to function. If this is acurate Peter you just freed up 10 of our licenses for other use.
Thank you / comments
Hello,
Can you verify this license agreement. Because when we purchased our 25 licenses we were told that it was per SQL instance regardless of if on the same server virtual or physical in fact whe...
We have seen this once using 4.0 on a server we restore transactions logs to hourly. We restarted the SQL server service to resolve it. We then updated to 4.1 and have not seen the problem come back.
Looking at our Red-Gate logs showed a sucessfull restore of a transaction log prior to it stop working.
Deleting database file 'e:\MSSQL\BACKUP\Datacenter_StandBy.bak'.
RESTORE LOG successfully processed 0 pages in 1.336 seconds (0.000 MB/sec).
We are running SQL Server 2000 SP4 on Windows 2003 Server SP1 32Bit / comments
We have seen this once using 4.0 on a server we restore transactions logs to hourly. We restarted the SQL server service to resolve it. We then updated to 4.1 and have not seen the problem come bac...
The Log Shipping option within Red-Gate offers some of this. For us, we wrote our own, we generate a backup with a stored proc with the Red-Gate command and then call a stored proc on the destination server telling it it is ready for restore and use the Red-Gate commands to restore. Has more details than that but that is the basics. The Red-Gate Log Shipping works, we just needed a few more items for our environment, so we started with what Red-Gate creates and added the items we needed here. / comments
The Log Shipping option within Red-Gate offers some of this. For us, we wrote our own, we generate a backup with a stored proc with the Red-Gate command and then call a stored proc on the destinati...
I really don't want to post my db names here but I can confirm we are past 128 char because the Script that is built for the transaction logs is specifying each db name, exec master..sqlbackup N'-SQL "BACKUP LOGS [1, 3, 3, 4, 5, 6, 7,8,9,10,11,12,13,14] TO DISK = ''G:\SQLBackup\<DATABASE>\<AUTO>'' WITH NAME = ''<AUTO>'', DESCRIPTION = ''<AUTO>'', ERASEFILES = 2, COMPRESSION = 2, THREADS = 1"', @exitcode OUTPUT, @sqlerrorcode OUTPUT
So I will need to break this down into multiple steps in the job. That will work.
Thanks / comments
I really don't want to post my db names here but I can confirm we are past 128 char because the Script that is built for the transaction logs is specifying each db name, exec master..sqlbackup N'-S...
Looking through the error codes it points to SQL Syntax error, not sure how this could be I used the GUI to build the scheduled jobs just like my other cluster and other servers. I can email you the script if needed. / comments
Looking through the error codes it points to SQL Syntax error, not sure how this could be I used the GUI to build the scheduled jobs just like my other cluster and other servers. I can email you th...
Well, when using Query Analyser to run the script, I get "Database name length exceeds maximum allowed length : db1,db2,*" (Actual names are longer) The issue is I have 18 Databases and only 14 of them do a transaction backup. Looks like a char length issue with the command in SQL Backup / comments
Well, when using Query Analyser to run the script, I get "Database name length exceeds maximum allowed length : db1,db2,*" (Actual names are longer) The issue is I have 18 Databases and only 14 of ...
That works, Thank you! / comments
That works, Thank you!
We ran into that also, All our backups are done to remote storage servers for holding to go to tape. I wonder if durring the install of SQLBackup 4.x if it should prompt for what ID/PW to use or select default local account (the dafault behavior) for the service account. Would simplify some support issues I bet. / comments
We ran into that also, All our backups are done to remote storage servers for holding to go to tape. I wonder if durring the install of SQLBackup 4.x if it should prompt for what ID/PW to use or se...