October 15, 2010 at 8:45 am
hai,
Can anyone post important SQL server interview question..
October 15, 2010 at 8:47 am
October 15, 2010 at 8:57 am
I don't why but almost every interview I've had I get asked about clustered index vs non clustered....
October 15, 2010 at 9:01 am
msmall 95832 (10/15/2010)
I don't why but almost every interview I've had I get asked about clustered index vs non clustered....
beacuse if you don't know the difference you shouldn't be at the interview
October 15, 2010 at 9:25 am
A list of questions is not going to get you through an interview. A competent interviewer can tell the difference between someone who has memorised answers and who knows the material.
Relax. Don't exaggerate your abilities. Don't lie. Don't be afraid to say 'I don't know', but have a plan for finding out.
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
October 15, 2010 at 10:38 am
GilaMonster (10/15/2010)
Relax. Don't exaggerate your abilities. Don't lie. Don't be afraid to say 'I don't know', but have a plan for finding out.
This. This this this. I passed more interviews in my early career with the answer of:
"F1. Search tab. Keyword1, Keyword2, Keyword3. Second, might be third, entry on the list, the one with 'T-SQL' instead of '.ASP'."
As an old manager of mine once trained me: Don't try to know ever answer, you won't learn enough. Learn every table of contents out there, so you know IF there's an answer, and where to research it when you need it.
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
October 15, 2010 at 10:49 am
msmall 95832 (10/15/2010)
I don't why but almost every interview I've had I get asked about clustered index vs non clustered....
Because for a lot of people, that's the trickiest SQL question they know the answer to. If you know it too, that makes you at least as knowledgeable as they are, by that standard.
When I was in the first grade (LONG time ago), kids would make statements like, "I'm smarter than you. I know e equals mc two!" We actually thought this proved something. (We were six years old, so we did have some excuse for that.)
I see this question being in somewhat the same category. People can often quote "the answer", and the interviewer will feel that they've tested something important, but neither party usually knows anything important about either thing.
So, if you want to come across as being "deep into SQL voodoo", learn the real differences. Don't just know that one controls the "order of the rows in the table", and one is "just an index", know the differences in storage, know what bookmark lookups are, know how they handle range scans, and when a scan is better than a seek in an execution plan (and the converse, of course). Know what a heap is, and the important differences between a non-clustered index on a heap and on an ordered table. Know the importance and use of "leading edges". Know what happens if you have multiple indexes with minor differences. Know how the engine picks which one to use, and how that relates to execution plan caching.
If you know all that, and understand it, you'll not only do well in interviews, but you'll be a better DBA for it.
After all, almost every interviewer asks that question. Which candidate is going to stick in their mind, the one who gives the minimum necessary answer, or the one who can plunge into the depths of the thing and get excited about the details? They'll have twenty people say, "you-can-only-have-one-clustered-index-and-it-controls-the-order-of-rows-in-the-table-but-you-can-have-many-nonclustered-indexes-and-they-are-stored-separately-on-the-disk-next-question-please", and they'll remember the 21st, who can explain the nitty gritty of it, without making the interviewer's eyes glaze over. Guess which one gets a follow-on interview, and probably gets the job...
(The not making the eyes glaze over part is just as important as knowing the data.)
Does that help?
(Keep in mind, last month, I was job hunting. I got 6 interviews in one week, and got an offer from every single one of those companies. So, there must be something to my technique on these things.)
- 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
October 16, 2010 at 1:09 am
It is not about memorize the list of interview questions, Just i want to get some ideas from it.Its like what are the concepts to be asked in the interview.I am expecting that info only..
October 16, 2010 at 1:13 am
GilaMonster (10/15/2010)
A list of questions is not going to get you through an interview. A competent interviewer can tell the difference between someone who has memorised answers and who knows the material.Relax. Don't exaggerate your abilities. Don't lie. Don't be afraid to say 'I don't know', but have a plan for finding out.
It is not about memorize the list of interview questions, Just i want to get some ideas from it.Its like what are the concepts to be asked in the interview.I am expecting that info only..
October 16, 2010 at 3:53 am
jaffrey (10/16/2010)
Its like what are the concepts to be asked in the interview.I am expecting that info only..
Who knows. It's not as if there's a standardised list that interviewers ask. It'll be different for every company, every interviewer, every candidate, etc.
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
October 18, 2010 at 11:04 am
jaffrey (10/16/2010)
It is not about memorize the list of interview questions, Just i want to get some ideas from it.Its like what are the concepts to be asked in the interview.I am expecting that info only..
I recently went through 6 tech screenings and interviews in one week. Of the 6, only 2 asked the same questions, and both of those were standardized online tests (www.ProveIt.com has about the stupidest DBA test in the world, and I took it twice that week).
One logged me into a copy of their dev server and had me poke around. No questions at all, just observation of what I do and what questions I ask.
One asked a lot of questions about SSIS basics.
One gave me a printout of some table definitions and asked me what was wrong with them.
The other asked questions about DR (backups, log shipping, mirroring, clustering, replication, et al).
So, no, there really isn't a way to go in knowing what they're likely to ask. Except for the questions about index types and backup types. If they ask anything at all, they'll probably include those two (see my prior reply for why I think that is so).
- 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 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply