January 14, 2016 at 10:47 pm
Comments posted to this topic are about the item Checkpoint
January 14, 2016 at 11:52 pm
This was removed by the editor as SPAM
January 15, 2016 at 12:06 am
Very good question, ran into this at my last company; after we were taken over a new infrastructure was introduced and their DB team consisted purely of developers, they did not see the need for a DBA.
...
January 15, 2016 at 1:01 am
I got one of Andy's right!!!!!
It's something I'd actually seen recently myself and I knew(!) the answer without looking it up. Of course being one of Andy's questions I then had to spend a good while researching things to make sure that was the most likely cause and there were no nasty surprises lurking.
How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537
January 15, 2016 at 7:34 am
BWFC (1/15/2016)
I got one of Andy's right!!!!!
Same reaction I had 😀
January 15, 2016 at 8:18 am
Hmm... what's wrong with checkdb, especially if the log file isn't full..... there's no reason your DB couldn't become corrupted since the last time you automatically checked it.
January 15, 2016 at 9:12 am
Nice question, thanks Andy!
January 15, 2016 at 9:20 am
Nice Question. But is this solution only confined to SQL 2012/2014? I thought we follow the same in the earlier editions too.
Thanks.
January 18, 2016 at 3:27 am
Great question, thanks Andy!
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 18, 2016 at 9:51 am
Nice question, Andy. There was enough there to get me thinking in different directions. I learned something new today because I've never seen that error. Thanks.
January 19, 2016 at 3:58 am
Good question.
I picked log full, but didn't notice that I should pick another. Carelessness that costs only worthless points in QotD, but in real life being careless about about a problem can be rather unfortunate :(.
The page referenced in the explanation is SQL 2016 only. For SQL 2014 and earlier it's a bit incomplete, perhaps - after that message it's quite likely that the backup log operation results (amongst other assorted messages) in something like
Msg 3052, Level 16, State 1, Line 4
BACKUP LOG was unable to log updates for database '<database name>'. Subsequent log backups will be required to advance the backup point from '<LSN id 1>' to '<LSN id 2>' after log space is made available for logging them.
and leaves you with a full log to which (due to a microsoft bug, fixed in SQL 2012 CU 8 and in SQL 2014 SP1 CU 3, but maybe you haven't applied the fix) you can't add files or extra space or back up again. If you haven't applied the fix, it might be useful to know how to tackle that one (kb/309516 has instructions.)
Tom
January 19, 2016 at 4:09 am
This was removed by the editor as SPAM
January 19, 2016 at 7:18 am
SQL-DBA-01 - not limited to SQL 2014, that's just where I tested. For QOTD I try to specify so that if it's different on other versions the readers have a fair chance. If I don't specify the version I've either checked the behavior on others or just want to make you think harder:-)
January 19, 2016 at 7:25 am
Andy Warren (1/19/2016)
SQL-DBA-01 - not limited to SQL 2014, that's just where I tested. For QOTD I try to specify so that if it's different on other versions the readers have a fair chance. If I don't specify the version I've either checked the behavior on others or just want to make you think harder:-)
They're both valid reasons, Andy. I won't comment on people flying off the handle, but getting us to consider everything just reinforces a part of our normal daily job.
January 19, 2016 at 7:50 am
Ed, I agree with that. It's harder than it looks to write a question that is challenging and what I call fair - enough that with the info given and some experience it's solvable. It's gotten to be my favorite writing challenge because as a group the people that work the QOTD are smart and great about providing feedback.
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply