Are the posted questions getting worse?

  • I'm wearing a Friday shirt.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • It is Friday for me. 😛 I am out tomorrow for field day at the kid's school.

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • I'm still waiting on last weeks friday!

  • Oops, I just replied on a thread started by someone who has asked me NOT to that. Guess that tarnishes my halo more.

  • Lynn Pettis (5/16/2013)


    Oops, I just replied on a thread started by someone who has asked me NOT to that. Guess that tarnishes my halo more.

    Wait. There's a thread where someone specifically asked you not to reply?

    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.

  • Brandie Tarvin (5/16/2013)


    Lynn Pettis (5/16/2013)


    Oops, I just replied on a thread started by someone who has asked me NOT to that. Guess that tarnishes my halo more.

    Wait. There's a thread where someone specifically asked you not to reply?

    And obviously Lynn has a hard time listening to the OP - hehe

    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

  • WayneS (5/16/2013)


    Chad Crawford (5/16/2013)


    The Dixie Flatline (5/16/2013)


    Not to mention alternate universes.

    But you just did.

    Darn those picky details...

    But I only mentioned it (that I know of) in this universe. What ARID (alternate reality identification) are you using? Is it the same one that has St. Lynn is going over to the dark side?

    __________________________________________________

    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 (5/16/2013)


    WayneS (5/16/2013)


    Chad Crawford (5/16/2013)


    The Dixie Flatline (5/16/2013)


    Not to mention alternate universes.

    But you just did.

    Darn those picky details...

    But I only mentioned it (that I know of) in this universe. What ARID (alternate reality identification) are you using? Is it the same one that has St. Lynn is going over to the dark side?

    Guys, guys. Didn't you know the ARID in SQL Server is broken?

    The SQL Server team at Microsoft attempted to update the DBCC Timewarp Paradox constraint in this latest round of updates, but forgot to check their math. They copied-n-pasted cells from Excel that were hidden (but should have been deleted) which caused Kepler to go into safe mode. Now the whole equation is kibbits and ARID is giving results based off alternating Stardates.

    There's like a whole future KB article about it that I can't link to because the Paradox constraint is still busted.

    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.

  • SQLRNNR (5/16/2013)


    Brandie Tarvin (5/16/2013)


    Lynn Pettis (5/16/2013)


    Oops, I just replied on a thread started by someone who has asked me NOT to that. Guess that tarnishes my halo more.

    Wait. There's a thread where someone specifically asked you not to reply?

    And obviously Lynn has a hard time listening to the OP - hehe

    Obviously. He just PMed me to remind me that he asked me not to visit his threads. Had to tell him sorry but I don't look at who posted, I just look at the question. Told him all he needed to do was ignore me. My posts could prove helpful to others even if he wants to ignore me.

  • Lynn Pettis (5/16/2013)


    SQLRNNR (5/16/2013)


    Brandie Tarvin (5/16/2013)


    Lynn Pettis (5/16/2013)


    Oops, I just replied on a thread started by someone who has asked me NOT to that. Guess that tarnishes my halo more.

    Wait. There's a thread where someone specifically asked you not to reply?

    And obviously Lynn has a hard time listening to the OP - hehe

    Obviously. He just PMed me to remind me that he asked me not to visit his threads. Had to tell him sorry but I don't look at who posted, I just look at the question. Told him all he needed to do was ignore me. My posts could prove helpful to others even if he wants to ignore me.

    First PM:

    kindly to not visit my forums. I'm sure you have bigger fish to fry. I just need some genuine help.

    My Response:

    Sorry, but I don't usually look at who posted the question, I just look at the question.

    To be honest, you really should not sweat the small stuff. All you have to do is just ignore me. My posts on your threads may help others even if you don't want to hear what I have to say.

    Second PM:

    no, they derail my posts. The post is first and foremost for me, secondly for all others having same problem.

    I'm just dropping it at this point.

  • Brandie Tarvin (5/16/2013)


    The Dixie Flatline (5/16/2013)


    WayneS (5/16/2013)


    Chad Crawford (5/16/2013)


    The Dixie Flatline (5/16/2013)


    Not to mention alternate universes.

    But you just did.

    Darn those picky details...

    But I only mentioned it (that I know of) in this universe. What ARID (alternate reality identification) are you using? Is it the same one that has St. Lynn is going over to the dark side?

    Guys, guys. Didn't you know the ARID in SQL Server is broken?

    The SQL Server team at Microsoft attempted to update the DBCC Timewarp Paradox constraint in this latest round of updates, but forgot to check their math. They copied-n-pasted cells from Excel that were hidden (but should have been deleted) which caused Kepler to go into safe mode. Now the whole equation is kibbits and ARID is giving results based off alternating Stardates.

    There's like a whole future KB article about it that I can't link to because the Paradox constraint is still busted.

    Under certain conditions, the built-in ARID methods can get stuck in infinite loops, causing the spacetime engine to spin off a steady stream of branched ARs until an out-of-range error for the ARID value terminates the batch. Unfortunately, to fix this, you have to track down the affected SQL Server instance in ALL AR branches and apply a hotfix at the moment each branch was created. This requires you to execute DBCC TIMEWARP from an instance of SQL Server 2005 (the last version not affected by this bug). If you don't have a 2005 instance handy, you can attempt the undocumented Bill and Ted method of creating one: "Remember to provision and install a SQL Server 2005 instance."

    Jason Wolfkill

  • Lynn Pettis (5/16/2013)


    no, they derail my posts. The post is first and foremost for me, secondly for all others having same problem.

    Yeah, Lynn, this is why we allow the original poster to moderate the responses . . . oh, yeah, we DON'T do that.

    😀

    Jason Wolfkill

  • Brandie Tarvin (5/16/2013)


    The Dixie Flatline (5/16/2013)


    WayneS (5/16/2013)


    Chad Crawford (5/16/2013)


    The Dixie Flatline (5/16/2013)


    Not to mention alternate universes.

    But you just did.

    Darn those picky details...

    But I only mentioned it (that I know of) in this universe. What ARID (alternate reality identification) are you using? Is it the same one that has St. Lynn is going over to the dark side?

    Guys, guys. Didn't you know the ARID in SQL Server is broken?

    The SQL Server team at Microsoft attempted to update the DBCC Timewarp Paradox constraint in this latest round of updates, but forgot to check their math. They copied-n-pasted cells from Excel that were hidden (but should have been deleted) which caused Kepler to go into safe mode. Now the whole equation is kibbits and ARID is giving results based off alternating Stardates.

    There's like a whole future KB article about it that I can't link to because the Paradox constraint is still busted.

    I thought PARADOX was a Borland product, competitive to SQL Server. It is in my ARID anyway, just like Excel. Microsoft should have imported the data from Excel to Quattro first.

    __________________________________________________

    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 (5/16/2013)


    Brandie Tarvin (5/16/2013)


    The Dixie Flatline (5/16/2013)


    WayneS (5/16/2013)


    Chad Crawford (5/16/2013)


    The Dixie Flatline (5/16/2013)


    Not to mention alternate universes.

    But you just did.

    Darn those picky details...

    But I only mentioned it (that I know of) in this universe. What ARID (alternate reality identification) are you using? Is it the same one that has St. Lynn is going over to the dark side?

    Guys, guys. Didn't you know the ARID in SQL Server is broken?

    The SQL Server team at Microsoft attempted to update the DBCC Timewarp Paradox constraint in this latest round of updates, but forgot to check their math. They copied-n-pasted cells from Excel that were hidden (but should have been deleted) which caused Kepler to go into safe mode. Now the whole equation is kibbits and ARID is giving results based off alternating Stardates.

    There's like a whole future KB article about it that I can't link to because the Paradox constraint is still busted.

    I thought PARADOX was a Borland product, competitive to SQL Server. It is in my ARID anyway, just like Excel. Microsoft should have imported the data from Excel to Quattro first.

    No, no, no, PARADOX of Borlands answer to Access. InterBase was Borlands competitor to SQL Server.

  • Lynn Pettis (5/16/2013)


    The Dixie Flatline (5/16/2013)


    Brandie Tarvin (5/16/2013)


    The Dixie Flatline (5/16/2013)


    WayneS (5/16/2013)


    Chad Crawford (5/16/2013)


    The Dixie Flatline (5/16/2013)


    Not to mention alternate universes.

    But you just did.

    Darn those picky details...

    But I only mentioned it (that I know of) in this universe. What ARID (alternate reality identification) are you using? Is it the same one that has St. Lynn is going over to the dark side?

    Guys, guys. Didn't you know the ARID in SQL Server is broken?

    The SQL Server team at Microsoft attempted to update the DBCC Timewarp Paradox constraint in this latest round of updates, but forgot to check their math. They copied-n-pasted cells from Excel that were hidden (but should have been deleted) which caused Kepler to go into safe mode. Now the whole equation is kibbits and ARID is giving results based off alternating Stardates.

    There's like a whole future KB article about it that I can't link to because the Paradox constraint is still busted.

    I thought PARADOX was a Borland product, competitive to SQL Server. It is in my ARID anyway, just like Excel. Microsoft should have imported the data from Excel to Quattro first.

    No, no, no, PARADOX of Borlands answer to Access. InterBase was Borlands competitor to SQL Server.

    Oh no, PARADOX pre-dated Access. Paradox is where I started as a developer. Then, after Access 2.0, they ported to windows and we got the most lovely programming language on earth (not), OPAL, Object Paradox Application Language. WOOF! What a dog.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

Viewing 15 posts - 39,736 through 39,750 (of 66,688 total)

You must be logged in to reply to this topic. Login to reply