SQL refresh - how?

[Olly]

I've got an interview coming up and it includes an SQL test. I've been a data analyst for years now but seldom need to write SQL directly, I just use the query builder interface in Access or MS SQL server.
I did a role a few years back that required me to understand, unravel and fix a lot of fairly complex SQL but I'm so rusty now I wouldn't fancy my chances in a test.

So...if I've got about 10 hours to invest it getting back up to speed what would you suggest as the best means to go about it?

Are there any books or sites out there that could really provide a "not for dummies" refresher please?

Thanks for the pointers

 

[MarillionFan]

I train data analysts and personally would have said the SQL was a key skill. Surprised you don't have it.

Are we talking SQL Server or Oracle? On the whole practice

Measures(Sum, Avg, Count, Distinct Count)
Case Statements
Cast & Convert
Date Manipulation
Inner and Outer Joins
Multiple Tables
Embedded SQL Statements
Group By
Having Clauses

That on the whole should give you the range of SQL you need for data analysis.

 

[Olly]

Thanks for the reply,
Yep, that's what I use day in day out, except replace case statements with IFs in Access. There's no need to "write" any of that if you use the graphical query builder functionality of Access/ SQL Server.

I find it way way faster

The reality is though whilst I'd have no problem reading SQL I'd have probs writing it from scratch seeing as I'm so rusty....hence the post. I do "have it" I just never need to use it so prob couldn't pass a test in it.

Answering your question, I believe the client uses the MS stack with the exception of ProClarity for reporting.

 

[MarillionFan]

So you've answered your own question Olly.

Practice the list(including embedded) on a Sql server instance until
you are comfortable building from
scratch. Should only take 1/2 a day and then you'll storm it

GL

MF

 

[Zippy]

Get the SQL Server Cheat Sheet and take it tucked inside your notepad. It should give you enough memory jogs.
Clustered vs non-clustered indexes comes up a lot too.

 

[Freamon]

Get the SQL Server Cheat Sheet and take it tucked inside your notepad. It should give you enough memory jogs.
Clustered vs non-clustered indexes comes up a lot too.

Clustered are the ones with rice krispies in, and non-clustered are the smooth variety, right?