|
Strips off and goes back to sleep. (5)
|
|
|
|
|
Little early, but not bad for a first attempt! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
Got it, but i'm in no position to do Monday (out of town, looking after 95yo Mum), so I'll clam up.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
|
Correct. Your turn next.
How is this the answer?
|
|
|
|
|
It was a bit obvious. I am normally crap at cryptic clues, but this one leapt out at me. 
|
|
|
|
|
|
 Congratulations!
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy Falcon.
|
|
|
|
|
My printer can print texts and image in colors, not only "D D D" 
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
But it still can be used to print a printer that can do more...
The user can't update the up: we update it for them (Choice in the CP poll)
|
|
|
|
|
A customer in Sarasota, FL called this morning with a strange issue. Connections to the sql database were successful, however any update/write operations were failing. Luckily an IT person was available to login to the remote server...I fully expected to see the db in recovery mode...but no, all appeared to be normal. 
I hate working on production servers, but here we are...
-1) delete the user and remap. Nope...fails with some weird message about the log file. I check the location, and there it is...but oddly, it hasn't been changed since last week???  Clue?
0) make a new backup. Nope fails with an error that the log file is not available...ok, at least getting somewhere
1) detach then reattach to maybe fix the log file issue. Nope, fails with the same error.
2) take the database offline. Nope, this never fails, but never finishes either.  Sorry dude, you'll have to kill that process (on your production server) to get out of it. 
3) getting desperate...check the logs. Hmmm, there was a spid deadlock that happened at around 9/10/2017 11:10 PM EDT, or at about the time that Irma was pounding Sarasota.
4) check for last backups...good, last one taken just an hour before this crap started.
5) last resort. ok, I'll try this, but really don't expect it to work...delete the database. This actually completed! Now, restore from the last backup...and we're in business again!
I'm assuming that the log file was locked or corrupted and that dropping the database was the only way out of it. Anyway, they didn't lose anything except the hour it took to troubleshoot. Is it Friday yet? 
"Go forth into the source" - Neal Morse
|
|
|
|
|
Did they not properly shut down their data center prior to the Irma's untimely arrival?
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
That was the same rhetorical question I asked when I saw the datetime of the event. I think the log speaks for itself! Also, of the dozen or so other databases on the server, this is the only one (known so far) to have been affected. Lucky me!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Foothill wrote: Did they not properly shut down their data center prior to the Irma's untimely known well in advance arrival?
FTFA
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Yea, it's not like they weren't forecasting Irma hitting Florida 5 days before it actually got there.
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
Total shock. Snuck right up on them
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
... so -2) wasn't necessary? (unslight R. E. Lee)
|
|
|
|
|
forgot to mention the option base -1! Actually, just lazy and didn't feel like renumbering as the recollection had changed to include a previous failed operation with a clue. -2) would have been the precursory under the breath swearing/praying that always accommodates having to work on someone else's production server.
"Go forth into the source" - Neal Morse
|
|
|
|
|
I think every now and then, it's the Irmas that's happening around Azure data centers. Last few months have been alright nevertheless.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy Falcon.
|
|
|
|
|
What database and what version?
Corrupted databases are something I saw rarely in the 90s but this is literally the first one I have even read about in at least 10 years.
To be fair when I say "database" I mean "relational database". I could make mongodb fail at will.
|
|
|
|
|
jschell wrote: What database and what version?
MS SQL Server 2008r2.
It was the first time I'd ever seen this happen...and I may be totally off on the corruption theory...I'm now thinking 'locked' instead...but bizarre nonetheless, and luckily, fairly easily solved with a full db drop and restore.
"Go forth into the source" - Neal Morse
|
|
|
|
|
Just saying that I would find it rather amazing if I saw a kangaroo hopping down my street. Rather surprising to me that there isn't a wild population somewhere in the US. Plenty of non-native squirrels and pythons so why not a few roos?
[^]
|
|
|
|
|
I had kangaroo at a dinner; enjoyed it.
I'd like to here from those in Australia. Do you hunt kangaroo, eat them? Thoughts?
|
|
|
|
|
Was she a good conversationalist?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
