100 Most famous interview Questions and Answers

  • Please go to the following link:-

    http://sqlcheatsheet.wordpress.com/2012/10/26/sql-server-2008-2008-r2-cheatsheet/

    Download the PDF (sqlserver2008r2_cheatsheet_v1-01.pdf). Password: harinam

    This is very good document for the freshup your memories with SQL Server features.

    Cheer's
    Rajesh

  • Says the password is incorrect. I tried copy and paste from your post as well as typing it in using both lower and upper case.

    Makr

  • It worked using just lower case.

    The document does not have a great format. It's hard to read.

    Luis C.
    General Disclaimer:
    Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

    How to post data/code on a forum to get the best help: Option 1 / Option 2
  • rajeshpalo2003 78748 (10/29/2012)


    Please go to the following link:-

    http://sqlcheatsheet.wordpress.com/2012/10/26/sql-server-2008-2008-r2-cheatsheet/

    Download the PDF (sqlserver2008r2_cheatsheet_v1-01.pdf). Password: Harinam

    This is very good document for the freshup your memories with SQL Server features.

    For all those who would use such a thing... Caveat Emptor!

    And while you're studying such canned answers, be advised that a lot of us don't ask canned questions on interviews especially for senior positions. For example...

    {Me} How many columns can a table have?

    {You} 1,024!

    {Me} So why are INSERTs designed to handle up to 4,096 columns?

    {You} {wtf???}

    --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)

  • {Me} How many columns can a table have?

    {You} 1,024!

    {Me} So why are INSERTs designed to handle up to 4,096 columns?

    {You} {wtf???}

    Something else to go and investigate 😀 Could be a QOTD

  • Jeff Moden (10/29/2012)


    rajeshpalo2003 78748 (10/29/2012)


    Please go to the following link:-

    http://sqlcheatsheet.wordpress.com/2012/10/26/sql-server-2008-2008-r2-cheatsheet/

    Download the PDF (sqlserver2008r2_cheatsheet_v1-01.pdf). Password: Harinam

    This is very good document for the freshup your memories with SQL Server features.

    For all those who would use such a thing... Caveat Emptor!

    And while you're studying such canned answers, be advised that a lot of us don't ask canned questions on interviews especially for senior positions. For example...

    {Me} How many columns can a table have?

    {You} 1,024!

    {Me} So why are INSERTs designed to handle up to 4,096 columns?

    {You} {wtf???}

    Or:

    {me} Why would you have table with that many columns?

    {Interviewee} ?????

  • mickyT (10/29/2012)


    {Me} How many columns can a table have?

    {You} 1,024!

    {Me} So why are INSERTs designed to handle up to 4,096 columns?

    {You} {wtf???}

    Something else to go and investigate 😀 Could be a QOTD

    The answer will be a huge surprise to those not used to this type of questioning... especially if I've already told them that the environmet they'll be working in is 2005 😉

    --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)

  • Lynn Pettis (10/29/2012)


    Jeff Moden (10/29/2012)


    rajeshpalo2003 78748 (10/29/2012)


    Please go to the following link:-

    http://sqlcheatsheet.wordpress.com/2012/10/26/sql-server-2008-2008-r2-cheatsheet/

    Download the PDF (sqlserver2008r2_cheatsheet_v1-01.pdf). Password: Harinam

    This is very good document for the freshup your memories with SQL Server features.

    For all those who would use such a thing... Caveat Emptor!

    And while you're studying such canned answers, be advised that a lot of us don't ask canned questions on interviews especially for senior positions. For example...

    {Me} How many columns can a table have?

    {You} 1,024!

    {Me} So why are INSERTs designed to handle up to 4,096 columns?

    {You} {wtf???}

    Or:

    {me} Why would you have table with that many columns?

    {Interviewee} ?????

    I know. To support a bad database design.

    The idea might be good for a cheat sheet (poorly executed) but it shouldn't be taken as a guide for a good interview.

    Luis C.
    General Disclaimer:
    Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

    How to post data/code on a forum to get the best help: Option 1 / Option 2
  • mickyT (10/29/2012)


    {Me} How many columns can a table have?

    {You} 1,024!

    {Me} So why are INSERTs designed to handle up to 4,096 columns?

    {You} {wtf???}

    Something else to go and investigate 😀 Could be a QOTD

    Actually, it could be two questions. One for SQL Server 2005 and one for 2008.

    But this is what I'm talking about. Even if all the answers in such cheat sheets were correct (and I assure you, they are not) and someone were able to recite every single answer without hesitation, they still wouldn't pass a real interview because such cheat sheets don't teach a person how to think and they certainly don't give you "experience" for a senior position.

    --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)

  • Luis Cazares (10/29/2012)


    Lynn Pettis (10/29/2012)


    Jeff Moden (10/29/2012)


    rajeshpalo2003 78748 (10/29/2012)


    Please go to the following link:-

    http://sqlcheatsheet.wordpress.com/2012/10/26/sql-server-2008-2008-r2-cheatsheet/

    Download the PDF (sqlserver2008r2_cheatsheet_v1-01.pdf). Password: Harinam

    This is very good document for the freshup your memories with SQL Server features.

    For all those who would use such a thing... Caveat Emptor!

    And while you're studying such canned answers, be advised that a lot of us don't ask canned questions on interviews especially for senior positions. For example...

    {Me} How many columns can a table have?

    {You} 1,024!

    {Me} So why are INSERTs designed to handle up to 4,096 columns?

    {You} {wtf???}

    Or:

    {me} Why would you have table with that many columns?

    {Interviewee} ?????

    I know. To support a bad database design.

    The idea might be good for a cheat sheet (poorly executed) but it shouldn't be taken as a guide for a good interview.

    Preeeeeeecisely.

    --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 (10/29/2012)For all those who would use such a thing... Caveat Emptor!

    And while you're studying such canned answers, be advised that a lot of us don't ask canned questions on interviews especially for senior positions.

    As correct as your response is, and I agree with it completely, the reality for many DBA position interviews is that they often begin with interviewers' pet questions about obscure facts and/or T-SQL coding examples. My experiences are that challenging interviewers as to why they think that some bit of trivia is important and/or useful usually backfires. They don't appreciate being asked to explain themselves.

    So, for dealing with reality, no matter how inappropriate it is, it doesn't hurt to try to be prepared for the inane questions that some interviewers think are important.

  • Lee Crain (10/31/2012)


    Jeff Moden (10/29/2012)For all those who would use such a thing... Caveat Emptor!

    And while you're studying such canned answers, be advised that a lot of us don't ask canned questions on interviews especially for senior positions.

    As correct as your response is, and I agree with it completely, the reality for many DBA position interviews is that they often begin with interviewers' pet questions about obscure facts and/or T-SQL coding examples. My experiences are that challenging interviewers as to why they think that some bit of trivia is important and/or useful usually backfires. They don't appreciate being asked to explain themselves.

    So, for dealing with reality, no matter how inappropriate it is, it doesn't hurt to try to be prepared for the inane questions that some interviewers think are important.

    I must be dealing with a different subset of interviewers than you are. I've never yet had that kind of question.

    Number of columns per table? That's trivia. Given the very meaning of "trivia", it's impossible for anyone to anticipate every piece of trivia that someone else might ask. One of the key laws of human interaction is always, always, always, "Everyone you meet knows things you don't." There's reciprocity for that, of course, in that you know things nobody else does.

    Theoretically, if I am ever asked that kind of question, I'd be inclined to answer something like, "I know there is an upper limit, but a properly normalized database should never approach that limit. If it ever does matter, I can look it up, but it's not something that's ever mattered to me yet."

    (Note, last time I was job hunting, I got 6 offers in 6 interviews, in 1 week. All at or above my asking salary, which was already higher than average for the market I'm in. Just to point out that my way of handling interview questions seems to work for me.)

    When I do the other side of it, if I ever asked such a "how many" type question, it would be a stress test more than a valid question. I'd probably ask something like, "How many flux capacitors does it take to implement a non-boolean Where clause in a semi-deterministic function?"

    Edit: Forgot to include the answer to the flux capacitors question. It's obviously 42, as everyone knows.

    - 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

  • I agree... I've never asked such trivial questions as to how many columns a table can hold for the very reasons that Gus stated. My point was meant to explain simply that wrote memorization of sometimes incorrect "trivial facts" are not sufficient to pass an interview unless the interviewer is also clueless.

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


    I agree... I've never asked such trivial questions as to how many columns a table can hold for the very reasons that Gus stated. My point was meant to explain simply that wrote memorization of sometimes incorrect "trivial facts" are not sufficient to pass an interview unless the interviewer is also clueless.

    On the other hand ... if anyone ever publishes "Trivial Pursuit, DBA Edition", they could come in very handy indeed!

    - 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

  • Does anyone ever ask or get asked what ACID properties are? I've been asked that one a number of times by non-DBA's grasping for interview questions. Whenever I interview DBA candidates, I am less impressed with what they can regurgitate than I am with real world scenario examples. I believe they call them "behavioral example" questions.

Viewing 15 posts - 1 through 15 (of 38 total)

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