Are the posted questions getting worse?

  • BBQ Mythbusters Style.

    Tenderize the meat with TNT!

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • 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

  • 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

  • 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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • 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

    http://www.sqlservercentral.com/Forums/FindPost957797.aspx

    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

  • 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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • 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.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

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