The BI School

02/08/2026

You've taken on a new work project ✅
The work will mean some SQL coding - yay!
But you ask for training, and you get 😶⛔❌.
So what are you going to do❓

Here's what:
You've got to go it alone, kiddo❗
Take it into your own hands👐.
Show some initiative🔋.
Sort it yourself.

Check out the SQL Superhero Program and your problems are solved.
https://thebischool.com/courses/sql-superhero-program/

01/08/2026

You want do better in your career, right? But to do better you need better technical skills, and that probably means SQL.

Our self-paced, flexible courses are tutor-mentored, meaning that you have an actual SQL expert on the end of a WhatsApp message, in the weekly group calls or on a one-to-one which you can book any time.

You 𝘤𝘰𝘶𝘭𝘥 do it yourself, or you could accept the help of someone who's helped hundreds of others and is waiting to help you.

Check it out here:
https://thebischool.com/courses/sql-superhero-program/

12/05/2026

I think that sometimes I'm trying to make up for my lost career years by helping others get started in their own careers.

That's why I teach SQL to career starters or mover-uppers looking for a promotion or simply hoping to be more effective in their current role.

And it doesn't have to cost a lot either.

I'm in the process of building a Skool training course to help get people started with SQL.

You can access it here: https://www.skool.com/learn-sql-for-free-9250

11/05/2026

I was given a task once to "See if I could do something with this very slow SQL query."

It was indeed very very slow - took over 36 hours to run as a background process.

The customer wanted to see if it could be sped up, and the task was passed to me.

The query contained CTEs. Lots of them. Maybe 30 or 40 from memory.

And although it wasn't handling huge amounts of data - we're talking 200k -300k - the CTEs were killing it.

Because CTEs are 'heaps' - that is, they are unindexed datasets.

This was in SQL Server, so I converted all the CTEs to temp tables. I gave each table a primary key - a clustered index, and applied some other indexes where needed.

Whilst at it, I tweaked some of the calculations, tidied the whole thing up, and fixed some other minor issues.

The new version of the query - the one that had temp tables instead of CTEs....

It ran in eleven seconds.

From 36 hours - to 11 seconds, all because of this small piece of work.

Knowing that this was what was required was down to experience, but this is the sort of thing we talk about at The BI School - real world examples and applications of the stuff you're learning.

This piece of work turned me into a rock star - at least within the context of that organisation and specifically with that one very happy customer.

Want to learn SQL?

Want to learn how to use SQL to give your career a rocket up the arse?

Visit www.thebischool.com today, and let's get you on your way.

10/05/2026

Window functions in SQL are an amazing addition to your arsenal.

Here are my top choices:

DENSE_RANK - this returns a ranking based on whatever criteria you set out, and partitioned however you choose too. I would use this to find the current and previous role that an employee has, or the top three highest earners by department for example. Very useful.

ROW_NUMBER - Simply returns a unique incremental value, one for each row in a dataset. Again these can be partitioned so you can reset the numbering when some other value changes such as region or product.

LAG/LEAD - these little gems have been two of the biggest game-changers ever in SQL. By referencing the next or previous row in a dataset, you can avoid multiple self joins or additional calculations. Has helped me reduce the size of some queries by around 80%.

SQL Window functions are very important to know.

If you'd like any further information on this or any other area of SQL, go to https://thebischool.com/courses/sql-superhero-program/

09/05/2026

Going for a promotion?

Lack of SQL skills blocking you?

It's a familiar tale.

Opportunities like this don't come round very often and typically, there's someone with more technical experience in the running.

Maybe it's one of your current colleagues - maybe it's an external candidate.

Doesn't matter.

The onus is on you to skill up - and fast.

So what are you going to do?

Visit www.thebischool.com and I'll help you.

08/05/2026

The three key skills for a career in data are:
1. Excel
2. A data vis tool e.g. Power BI, Tableau, Looker etc.
3. SQL

Nail these and you're well on your way.

Excel is the foundational skill for working with data. It's not just about presenting data in tables and charts, it's also about ninja skills with formulae such as lookups and complex calculations.

Working with data visualisation tools is where you get noticed. Again, there's more to it than simply using charts and graphs, even when they're all fancy and interactive. There's the query editor, DAX and understanding the underlying data model.

As for SQL - well that's where you place yourself high above all the other candidates for roles because, let's face it, EVERYONE has Excel and a data vis tool, so how do you stand out?

SQL.

If you're already learning SQL, this might help. It's a Cheat-Sheet covering the basic commands, syntax and query structure.

https://thebischool.com/cheats-postgresql/

It's proving quite popular, so grab a copy now.

This guide will help you remember those key commands, functions and syntax when working in PostgreSql

07/05/2026

FREE - SQL Cheat Sheet - PostgreSql

Help yourself to your own free SQL cheat-sheet, written for PostgreSql.

Print it out and keep it by your desk, or open it in a web browser and save it as a favourite.

Here it is...

This guide will help you remember those key commands, functions and syntax when working in PostgreSql