Few interview questions

Question

Few interview questions

Viewing 4 posts - 16 through 18 (of 18 total)

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

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

That is a topic that gets endlessly debated. There's no right or wrong side, just preferences.

Myself, I don't like 'N/A' or 'unknown' records scattered all over my DB, so I prefer to leave columns NULL if they are not applicable or unknown.

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

Ewan Hampson SSCrazy Points: 2780 More actions · Answer 2

That is a topic that gets endlessly debated

I was just wondering whether an interviewer might be testing whether the candidate is alert to the debate as well as able to give a technical reply.

J-440512 SSCertifiable Points: 6285 More actions · Answer 3

"if we exclude the performance point ...is it possible to have these many indexes..."

Why bother with indexes in the first place when the performance is not even a consideration ?

What's the point ?

Jeff Moden SSC Guru Points: 1004341 More actions · Answer 4

Heh... the point is that Interviewer's ask some of the darnedest questions to find out if you really know instead of just memorizing a list of "interview questions". 🙂

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