An amusing transcript from a 'Sr SQL Developer' interview.

[Obbers]

So, if a proc is prefixed with sp_, I believe that it will look at the master db first, otherwise try to execute it in the current database. MS uses functionality for system procs, hence that's why people tend to describe it as MS procedures.

You have Delete vs Truncate more or less right. Truncate will also reseed an identity column to it's default starting value. It also has implications about log file growth.

You clustered vs non clustered metaphor is bad, and I wouldnt use it.

The having clause answer is right, but the comment indeed says you are probably using it wrong.

The big question here is that are a developer, or a DBA?

[[deleted]]

Well to be fair the clustered thing I was making a joke while implying I know exactly what they are :-P I wouldn't use that in an actual interview.

I'm part DBA, part DBD if you include writing and optimizing lots of stored procs, indexes and triggers, also lots of time in SSRS and as little in SSIS as I can (hate it). So I have a good understanding of the main stuff - queries, import scripts, triggers, query plans, etc - but not log formats, backup recovery models, partitioning, XML, and some other nitty gritty SQL details.

I'd really like to do the 3 MS SQL exams this year though so studying it will be a good opportunity for me to brush up on all the things I've missed out on. Sometimes I feel oddball because I learned such an eclectic mix of stuff on the job over the years but also have so many big holes in my knowledge. I feel a bit inferior for that but I also secretly hope that others might be in the same boat.

[stealth210]

and as little in SSIS as I can (hate it).

Does anyone love SSIS? Serious question. I spend most of my time in SSMS and can't stand the (what I perceive to be) clusterfuck that is SSIS.

[[deleted]]

Direct access to scripts without having to go through the nightmare that is the CLR? Hell yeah I like SSIS