July 28, 2010 at 12:18 pm
BBQ Mythbusters Style.
Tenderize the meat with TNT!
July 28, 2010 at 12:19 pm
CirquedeSQLeil (7/28/2010)
I reject your reality and substitute my own
Hasn't the Thread already done that? Or is it going to do that? Wait... what time is it again?
Wow... that DBCC TIMEWARP thing really worked... I mean... umm... which reality are we running on now? And do you have quality hampster poo here so I can refuel the TIMEWARP?
-- Kit
July 28, 2010 at 12:25 pm
Congrats to Kassandra, Lynn. Definitely cool bragging rights. Best wishes to her at West Point. I'm sure she will do well once she gets there. 😀
-- Kit
July 28, 2010 at 12:26 pm
Brandie Tarvin (7/28/2010)
BBQ Mythbusters Style.Tenderize the meat with TNT!
Absolutely - it will be cooked too!! Bonus:w00t:
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 28, 2010 at 12:37 pm
Can I borrow a cup of reality? I need it to for a homemade BBQ sauce recipe....
__________________________________________________
Against stupidity the gods themselves contend in vain. -- Friedrich Schiller
Stop, children, what's that sound? Everybody look what's going down. -- Stephen Stills
July 28, 2010 at 12:42 pm
All the BBQ talk started a problem. I have now convinced 8 people in the office to go for BBQ for lunch.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 28, 2010 at 12:44 pm
Problem?
I see no problem.
__________________________________________________
Against stupidity the gods themselves contend in vain. -- Friedrich Schiller
Stop, children, what's that sound? Everybody look what's going down. -- Stephen Stills
July 28, 2010 at 12:47 pm
The Dixie Flatline (7/28/2010)
Problem?I see no problem.
The problem is that lunch is still a bit off. I am hungry now, want BBQ now, and have to wait.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 28, 2010 at 1:07 pm
The Dixie Flatline (7/28/2010)
Can I borrow a cup of reality?
<checks around kitchen> Sorry. Fresh out. Think I used the last of it at a client to try and turn an unbelievable situation into something just very strange. I suspect the jar was past its use-by date as it had no effect.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 28, 2010 at 2:31 pm
I've been out for weeks. Thanks for checking, Gail.
:crying:
__________________________________________________
Against stupidity the gods themselves contend in vain. -- Friedrich Schiller
Stop, children, what's that sound? Everybody look what's going down. -- Stephen Stills
July 28, 2010 at 6:22 pm
GilaMonster (7/28/2010)
There have been some really 'entertaining' questions lately. There have been some 'entertaining' replies too.So far this week I've seen two different people advocating backing the log up in Simple recovery.
But were those replies the equivalent of sending off the apprentice to fetch a bucket full of holes (or asking the trainee programmer to write some ideas on how to incorporate a driver for the GSD) or were they serious?
Tom
July 29, 2010 at 2:47 am
Tom.Thomson (7/28/2010)
GilaMonster (7/28/2010)
There have been some really 'entertaining' questions lately. There have been some 'entertaining' replies too.So far this week I've seen two different people advocating backing the log up in Simple recovery.
But were those replies the equivalent of sending off the apprentice to fetch a bucket full of holes (or asking the trainee programmer to write some ideas on how to incorporate a driver for the GSD) or were they serious?
Serious advice, or that's what it looked like.
http://www.sqlservercentral.com/Forums/FindPost959438.aspx - probably more of a 'skip steps' than anything else
http://www.sqlservercentral.com/Forums/FindPost957797.aspx
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 29, 2010 at 5:07 am
GilaMonster (7/29/2010)
Serious advice, or that's what it looked like.http://www.sqlservercentral.com/Forums/FindPost959438.aspx - probably more of a 'skip steps' than anything else
Amazing, especially the one from someone who's apparently an MVP. Perhaps he meant use explorer to make a copy rather of the log rather than do a log backup; but I don't fancy anyones chances of doing any recovery to an earlier point in time from such a copy when the recovery model is SIMPLE, since there's always a good chance that the earliest surviving log entry is later than the db state of the last full or incremental backup.
Tom
July 29, 2010 at 5:24 am
Tom.Thomson (7/29/2010)
Amazing, especially the one from someone who's apparently an MVP.
My thoughts exactly. He is an MVP. I searched for his MVP profile on the microsoft site and he does have one.
Perhaps he meant use explorer to make a copy rather of the log rather than do a log backup; but I don't fancy anyones chances of doing any recovery to an earlier point in time from such a copy when the recovery model is SIMPLE, since there's always a good chance that the earliest surviving log entry is later than the db state of the last full or incremental backup.
What probably would work is, at the point of the 'oops', take the DB offline, copy the files elsewhere (both mdf and ldf), attach as new DB and mark readonly. Then, if a log reader is bought, it should be able to go through the log of the read-only DB and pick up the log records. They'll be inactive, but they should still be there. Has to be done just about immediately though, not a day or two later
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 29, 2010 at 6:54 am
GilaMonster (7/29/2010)
What probably would work is, at the point of the 'oops', take the DB offline, copy the files elsewhere (both mdf and ldf), attach as new DB and mark readonly. Then, if a log reader is bought, it should be able to go through the log of the read-only DB and pick up the log records. They'll be inactive, but they should still be there. Has to be done just about immediately though, not a day or two later
That's actually a good idea. Not that I need this now, but I should keep this in mind for future problems. Thanks, Gail.
Viewing 15 posts - 16,861 through 16,875 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply