Are the posted questions getting worse?

  • Greg Edwards-268690 (1/31/2012)


    Evil Kraig F (1/31/2012)


    Greg Edwards-268690 (1/31/2012)


    Brandie Tarvin (1/31/2012)


    Greg Edwards-268690 (1/31/2012)


    Brandie Tarvin (1/31/2012)


    SQLRNNR (1/31/2012)


    Greg Edwards-268690 (1/31/2012)


    Koen Verbeeck (1/31/2012)


    Greg Edwards-268690 (1/31/2012)


    Must have been the 3rd table that caused the confusion.

    Book only showed 2 in an example.

    😀

    Shows what happens when I think - other people laugh at me.:-P

    With three tables in the join, how can I write that triangle in code? Worse, what if more tables get added, how do i create a polygon in tsql?

    I have actually had to create code for a triangle table IRL for our actuarial team. Talk about pain!

    Geometry must be a skill to master in order to become SQL Expert.

    Maybe as interview question, explain geometric relationship used in sample query?

    YIKES! If people are going to start asking me that at interviews, I'd best go back and review that code, plus recreate it with all the new T-SQL techniques so I'm not using bassakwards 2000 T-SQL techniques.

    I was thinking along the lines of the popular answers to interview question threads that some seem to want to memorize and become true experts. It would be fun in the right setting to ask that and see the response.:w00t:

    An icebreaker.....

    Interviewer: Explain using geometry components in SQL Server.

    Me: ... ... ... Oh, wait, you're serious? You put them there until you decide you've lost your mind, then go get software that does it for you.

    Wait? or Octagon?

    Sounds like you use them as placeholders.

    I will have to test, although it might be hard for me to determine when I have lost my mind.

    A link for SQL geometry.

    http://msdn.microsoft.com/en-us/library/cc280487.aspx

    What I'm waiting for is the SQL Astrology data type. That way I can write joins on people who are compatible.

  • OCTom (1/31/2012)[hr

    A link for SQL geometry.

    http://msdn.microsoft.com/en-us/library/cc280487.aspx

    What I'm waiting for is the SQL Astrology data type. That way I can write joins on people who are compatible.

    Would those be left, right, or inner joins? I suppose a self join would be out! 🙂

    The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge. - Stephen Hawking

  • Steve Jones - SSC Editor (1/31/2012)


    SQL Kiwi (1/31/2012)


    Ok, the embedded quotes occupy a whole screen now...

    I need a filter to whack multiple embedded quotes. It can be quite annoying.

    I think they're kind of cool. If you press and hold "Page Down", it looks like a movie. 😛

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Capt. Sigerson (1/30/2012)


    As someone with lots of DBMS experience, but new to SQL Server, I have found the SSC community to be an invaluable resource. I try to use BOL to find answers, or at least show me how to phrase my question so that no one will have to waste time deciphering it. I remember this from something I read long ago: "to ask a truly intelligent question requires that you already know 90% of the answer."

    It's that last 10% that is the hardest and the SSC community has always stepped up on any question I've asked. Not just answering questions at hand, but proposing alternate information sources and tips on best practices, and ... the list goes on.

    Thanks to all of you for putting up with the aggravation; some of us appreciate it very much.

    This is the kind of post that helps keep us going. Thanks Capt.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Near the beginning of the month, my boss says "why aren't these files being removed from the Inbound folder? Add a task to this SSIS package that deletes them as soon as the package is done processing."

    I nod, agree and-being the paranoid dba that I am-promptly disobey him. I add the task to the package, but instead of deleting the files, I decide to zip them and hide them in another folder. Yes, he will probably shake his finger at me some point in the future when he discovers the trove of disk-devouring archive zips, but it'll be worth if it there's ever a problem, I tell myself. I can handle the lecture.

    Two days later, he comes running to my desk. "You haven't done the archive off task I told you to, have you? Please tell me you haven't deleted those files. We need to recreate XYZ!"

    I smile. "Why, yes, I did create that task and run it against production, but I decided to put the files here." I point him to the directory and the boss is very happy and relieved that paranoia is my watchword. But now he's got his own paranoia thing going. The monthly files will be delivered tomorrow and I have once again been asked to make sure the old files were archived and that the new files will be zipped and saved once the package is done running. No discussions of deletes these days, my friends. No, Siree.

    Of all the skills a DBA should have, I'm beginning to think a healthy dose of paranoia should be on the required list. Agree? Disagree?

    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 (1/31/2012)


    Of all the skills a DBA should have, I'm beginning to think a healthy dose of paranoia should be on the required list. Agree? Disagree?

    It's only paranoia if the world ISN'T out to get you. Otherwise it's called a healthy regard for your own sanity and wellbeing.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • Brandie Tarvin (1/31/2012)


    Of all the skills a DBA should have, I'm beginning to think a healthy dose of paranoia should be on the required list. Agree? Disagree?

    I think you're involved in some sort of plot. :ermm:

  • Brandie Tarvin (1/31/2012)


    Of all the skills a DBA should have, I'm beginning to think a healthy dose of paranoia should be on the required list. Agree? Disagree?

    It's a frequent story amongst DBAs. The 11th Commandment is "Though shalt not kill data." 😛

    Even more fun is a take I did on Azimov's 3 laws of robotics for DBAs. I'll see if I can find it again. I whole heartedly agree with Craig, though... it's not paranoia... it's protecting everyone's butt even if they don't know it needs protecting yet.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Jeff Moden (1/31/2012)


    Brandie Tarvin (1/31/2012)


    Of all the skills a DBA should have, I'm beginning to think a healthy dose of paranoia should be on the required list. Agree? Disagree?

    It's a frequent story amongst DBAs. The 11th Commandment is "Though shalt not kill data." 😛

    Even more fun is a take I did on Azimov's 3 laws of robotics for DBAs. I'll see if I can find it again. I whole heartedly agree with Craig, though... it's not paranoia... it's protecting everyone's butt even if they don't know it needs protecting yet.

    Something like:

    A robot DBA may not injure data or, through inaction, allow data to come to harm.

    A robot DBA must obey the orders given to it by managers, except where such orders would conflict with the First Law.

    A robot DBA must protect its own existence as long as such protection does not conflict with HIPAA, SOX.

    That sounded better in my head, but SOX overrides the managers, so it loses the whole 'previous law' thing.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • Brandie Tarvin (1/31/2012)


    Of all the skills a DBA should have, I'm beginning to think a healthy dose of paranoia should be on the required list. Agree? Disagree?

    Agree.

    Just because you're paranoid, don't mean they're not after you.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Koen Verbeeck (1/31/2012)


    Brandie Tarvin (1/31/2012)


    Of all the skills a DBA should have, I'm beginning to think a healthy dose of paranoia should be on the required list. Agree? Disagree?

    Agree.

    Just because you're paranoid, don't mean they're not after you.

    Coincedence?

    http://www.sqlservercentral.com/articles/Raw+Materials/70852/[/url]

    Agree totally.

  • MysteryJimbo (2/1/2012)


    Koen Verbeeck (1/31/2012)


    Brandie Tarvin (1/31/2012)


    Of all the skills a DBA should have, I'm beginning to think a healthy dose of paranoia should be on the required list. Agree? Disagree?

    Agree.

    Just because you're paranoid, don't mean they're not after you.

    Coincedence?

    http://www.sqlservercentral.com/articles/Raw+Materials/70852/[/url]

    Agree totally.

    Someone paranoid would say:

    no, definately no coincedence.

    😀

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • MysteryJimbo (2/1/2012)


    Koen Verbeeck (1/31/2012)


    Brandie Tarvin (1/31/2012)


    Of all the skills a DBA should have, I'm beginning to think a healthy dose of paranoia should be on the required list. Agree? Disagree?

    Agree.

    Just because you're paranoid, don't mean they're not after you.

    Coincedence?

    http://www.sqlservercentral.com/articles/Raw+Materials/70852/[/url]

    Agree totally.

    Wow. How did I miss that one? Love it!

    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 (1/31/2012)


    Near the beginning of the month, my boss says "why aren't these files being removed from the Inbound folder? Add a task to this SSIS package that deletes them as soon as the package is done processing."

    I nod, agree and-being the paranoid dba that I am-promptly disobey him. I add the task to the package, but instead of deleting the files, I decide to zip them and hide them in another folder. Yes, he will probably shake his finger at me some point in the future when he discovers the trove of disk-devouring archive zips, but it'll be worth if it there's ever a problem, I tell myself. I can handle the lecture.

    Two days later, he comes running to my desk. "You haven't done the archive off task I told you to, have you? Please tell me you haven't deleted those files. We need to recreate XYZ!"

    I smile. "Why, yes, I did create that task and run it against production, but I decided to put the files here." I point him to the directory and the boss is very happy and relieved that paranoia is my watchword. But now he's got his own paranoia thing going. The monthly files will be delivered tomorrow and I have once again been asked to make sure the old files were archived and that the new files will be zipped and saved once the package is done running. No discussions of deletes these days, my friends. No, Siree.

    Of all the skills a DBA should have, I'm beginning to think a healthy dose of paranoia should be on the required list. Agree? Disagree?

    Agreed completely. Every time someone asks me to delete anything, I find a place to archive it first. After having a some form of the "are you absolutely positively sure you'll never want this again"? discussion.

    One of our execs is still looking for data from about 10 years ago that my predecessor deleted for him.

    -Ki

  • Brandie Tarvin (1/31/2012)


    Near the beginning of the month, my boss says "why aren't these files being removed from the Inbound folder? Add a task to this SSIS package that deletes them as soon as the package is done processing."

    I nod, agree and-being the paranoid dba that I am-promptly disobey him. I add the task to the package, but instead of deleting the files, I decide to zip them and hide them in another folder. Yes, he will probably shake his finger at me some point in the future when he discovers the trove of disk-devouring archive zips, but it'll be worth if it there's ever a problem, I tell myself. I can handle the lecture.

    Two days later, he comes running to my desk. "You haven't done the archive off task I told you to, have you? Please tell me you haven't deleted those files. We need to recreate XYZ!"

    I smile. "Why, yes, I did create that task and run it against production, but I decided to put the files here." I point him to the directory and the boss is very happy and relieved that paranoia is my watchword. But now he's got his own paranoia thing going. The monthly files will be delivered tomorrow and I have once again been asked to make sure the old files were archived and that the new files will be zipped and saved once the package is done running. No discussions of deletes these days, my friends. No, Siree.

    Of all the skills a DBA should have, I'm beginning to think a healthy dose of paranoia should be on the required list. Agree? Disagree?

    We had to fire a contractor yesterday because of lack of useful work on his part (both quantity and quality had issues). I've already begun changing passwords on servers, even ones he didn't have access to. As I told my boss, "I'm the DBA. I'm paid to be paranoid about our data and the security on it."

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

Viewing 15 posts - 34,081 through 34,095 (of 66,712 total)

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