Activity overview
Latest activity by KatanaCS
Yeah, had a hunch that was the case. 8)
Thanks for all your help!! / comments
Yeah, had a hunch that was the case. 8)
Thanks for all your help!!
Well, it's been 2 weeks since I started using the new EXE and we haven't had an error on that server. Looks like it worked!
I have a number of other servers where the error is happening; what are my next steps for fixing those? Should I put this version into place and wait for a future release, or something else?
Thanks!! / comments
Well, it's been 2 weeks since I started using the new EXE and we haven't had an error on that server. Looks like it worked!
I have a number of other servers where the error is happening; what are ...
Sorry, just realized I wasn't watching this post.
Yes, we're performing both backups and restores on this server every day. / comments
Sorry, just realized I wasn't watching this post.
Yes, we're performing both backups and restores on this server every day.
Ok, I replaced it and ran to test, but it's no longer writing to SQBCoreService_log.txt; is it supposed to? / comments
Ok, I replaced it and ran to test, but it's no longer writing to SQBCoreService_log.txt; is it supposed to?
Ok, I've put this into place.
It's no trouble, it's obviously some odd hidden bug, such as "if it's Tuesday and it's raining, do something obscure ...". I'm just glad you guys are so responsive! 8) / comments
Ok, I've put this into place.
It's no trouble, it's obviously some odd hidden bug, such as "if it's Tuesday and it's raining, do something obscure ...". I'm just glad you guys are so responsive!...
Compression Analyzer - Authentication Bug
Hi,
I'm not 100% sure if this post should be here or somewhere else, but I couldn't find a defined group for Compression Analyzer.
I just tried to use the Compression Analyzer to estimate a databas...
Just got an error, and here are the last two sessions worth of data from the log file:
2/21/2008 10:45:01 AM : dbadmin:SIMPLE:0:0
2/21/2008 10:45:01 AM : distribution:SIMPLE:0:0
2/21/2008 10:45:01 AM : LogShip_Test:BULK_LOGGED:0:0
2/21/2008 10:45:01 AM : master:SIMPLE:0:0
2/21/2008 10:45:01 AM : model:SIMPLE:0:0
2/21/2008 10:45:01 AM : msdb:SIMPLE:0:0
2/21/2008 10:45:01 AM : tempdb:SIMPLE:0:0
2/21/2008 10:45:01 AM : ThrivaAdmin:BULK_LOGGED:0:0
2/21/2008 10:45:01 AM : ThrivaAdminMaster:BULK_LOGGED:0:0
2/21/2008 10:45:01 AM : ThrivaCore:BULK_LOGGED:0:0
2/21/2008 10:45:01 AM : ThrivaCoreMaster:BULK_LOGGED:0:0
2/21/2008 10:45:01 AM : ThrivaJournal:BULK_LOGGED:0:0
2/21/2008 10:45:01 AM : ThrivaManagement:BULK_LOGGED:0:0
2/21/2008 11:00:01 AM : dbadmin::0:
2/21/2008 11:00:01 AM : distribution::0:
2/21/2008 11:00:01 AM : LogShip_Test:BULK_LOGGED:0:0
2/21/2008 11:00:01 AM : master:SIMPLE:0:0
2/21/2008 11:00:01 AM : model:SIMPLE:0:0
2/21/2008 11:00:01 AM : msdb:SIMPLE:0:0
2/21/2008 11:00:01 AM : tempdb:SIMPLE:0:0
2/21/2008 11:00:01 AM : ThrivaAdmin::0:
2/21/2008 11:00:01 AM : ThrivaAdminMaster::0:
2/21/2008 11:00:01 AM : ThrivaCore:BULK_LOGGED:0:0
2/21/2008 11:00:01 AM : ThrivaCoreMaster::0:
2/21/2008 11:00:01 AM : ThrivaJournal::0:
2/21/2008 11:00:01 AM : ThrivaManagement::0:
It would seem the recovery model value wasn't captured on the run with the error. / comments
Just got an error, and here are the last two sessions worth of data from the log file:
2/21/2008 10:45:01 AM : dbadmin:SIMPLE:0:0
2/21/2008 10:45:01 AM : distribution:SIMPLE:0:0
2/21/2008 10:45:01 ...
Ok, I have the new EXE in place.
Thanks for the help! / comments
Ok, I have the new EXE in place.
Thanks for the help!