How can we help you today? How can we help you today?
brosato
Activity overview Badges (0) Posts (16) Comments (57)

Comments

Sort by recent activity
Thanks, Unfortunately, we have encrypted objects. Good to hear it's logged as an issue. / comments
  1. Community
  2. SQL Compare Previous Versions
  3. For Pete's sake already. DBCC TRACEON/TRACEOFF 3604
Thanks, Unfortunately, we have encrypted objects. Good to hear it's logged as an issue.
0 votes
All my test restores went off without a hitch last night. Thanks Pete. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. restore time VERY slow (compared to native SQL restore)
All my test restores went off without a hitch last night. Thanks Pete.
0 votes
Everything seems to be working ok now. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. restore time VERY slow (compared to native SQL restore)
Everything seems to be working ok now.
0 votes
I think that took care of it. I'm going to try something a bit larger with more files. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. restore time VERY slow (compared to native SQL restore)
I think that took care of it. I'm going to try something a bit larger with more files.
0 votes
petey wrote: Can you back up using 6.4.0.1015? Can you back up a small database and restore it? Thanks. Here's what happening. If I specify the filename of a full backup, [\\Recovery\SQLBackups\Nasdaq\CustomerViews\FULL_CustomerViews_20100811_083903.sqb], it will restore. If I use [\\Recovery\SQLBackups\Nasdaq\CustomerViews\*.sqb] LATEST_FULL the restore never starts. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. restore time VERY slow (compared to native SQL restore)
petey wrote: Can you back up using 6.4.0.1015? Can you back up a small database and restore it? Thanks. Here's what happening. If I specify the filename of a full backup, [\\Recovery\SQLBack...
0 votes
Restore never starts at all with 6.4.0.1015. Process is waiting on PREEMPTIVE_OS_GETPROCADDRESS. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. restore time VERY slow (compared to native SQL restore)
Restore never starts at all with 6.4.0.1015. Process is waiting on PREEMPTIVE_OS_GETPROCADDRESS.
0 votes
petey wrote: As per my last post, could you please check if SQL Backup generated a stack trace when it appeared to hanged? This stack trace is stored in a file named SQBCoreService_<instance name>_bugreport.txt, and is located in 'C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\' on Windows 2003 and older, and 'C:\ProgramData\Red Gate\SQL Backup\Log\' on Windows Vista and newer. Also, how large is your backup file? Would it be possible/feasible to send us a copy? Thanks. There is no file by that name in that directory. There are other log files. The backup file I'm trying to restore right now is 430MB. If I look in the GUI under the in progress tab, it processed up to 4.5GB and stopped. I just restored one that was twice that size but it took 5 times before it finished. I though it might be because the files were on a network share so I copied them local. Still doesn't work. This is our Great Plains database so I don't believe I can send it to you. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. restore time VERY slow (compared to native SQL restore)
petey wrote: As per my last post, could you please check if SQL Backup generated a stack trace when it appeared to hanged? This stack trace is stored in a file named SQBCoreService_<instance nam...
0 votes
I just reverted back to 6.4.0.56 and the restore finished. Strangely enough, the processed size reported in the GUI was 4.5GB. So it seems the other one got to the end but would never finish. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. restore time VERY slow (compared to native SQL restore)
I just reverted back to 6.4.0.56 and the restore finished. Strangely enough, the processed size reported in the GUI was 4.5GB. So it seems the other one got to the end but would never finish.
0 votes
I can't get differential restores to finish. They just hang once they get to a certain point. Actually, restores of full backups hang too. <edit> There must be something wrong with the latest build I'm using to fix the LATEST_ALL bug. Restores are hit or miss and it doesn't matter what the size is. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. restore time VERY slow (compared to native SQL restore)
I can't get differential restores to finish. They just hang once they get to a certain point. Actually, restores of full backups hang too. <edit> There must be something wrong with the latest buil...
0 votes
I'm still plagued with problems. Here's the latest from the GUI SQLBackup. Crash! Object reference not set to an instance of an object. WorkerExecutionException at RedGate.SQLBackup.Engine.ConfigurableThreadPool.a(Exception ) at RedGate.SQLBackup.Engine.ConfigurableThreadPool.a.b() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() NullReferenceException Object reference not set to an instance of an object. at g.a(SqlConnection , aD ) at g.b(Object ) / comments
  1. Community
  2. SQL Backup Previous Versions
  3. restore time VERY slow (compared to native SQL restore)
I'm still plagued with problems. Here's the latest from the GUI SQLBackup. Crash! Object reference not set to an instance of an object. WorkerExecutionException at RedGate.SQLBackup.Engine.Config...
0 votes
Total activity
92
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
19