Today I had cause to take a slightly different direction with a database that had stood for many years providing a fairly critical business function. The change of direction involved dropping a few columns out of a core table with references across an unknown number of procedures and views. What could go wrong?! Let me start by saying that whilst I spend a lot of time in SQL Server, I’m no DBA and there may well be easier ways of doing this, but in years gone by I would have kicked off by trawling through system tables to find occurrences of the column in question. This worked, but it’s a little clunky and I always had...
I usually run private workshops around these, here's the upcoming public events I'll be at:
- DDD: 3 Dec, Brisbane (Australia)
- Workshop: Hack Yourself First: How to go on the Cyber-Offence: 16-17 Jan, London (United Kingdom)
- NDC London: 18-20 Jan, London (United Kingdom)
- Workshop: Hack Yourself First: How to go on the Cyber-Offence: 25-26 Jan, Leuven (Belgium)
- ZIONSECURITY Conference: 27 Jan, Leuven (Belgium)
- Here's how I verify data breaches
- When a nation is hacked: Understanding the ginormous Philippines data breach
- The world needs more stupid security researchers – join me!
- It’s time that you – the vulnerable human – brush up on your social engineering skills with Pluralsight
- How I optimised my life to make my job redundant