Triton Db2 Geek

Confessions of a DB2 geek

IBM Gold Consultant Program and IBM Premier business Partner

Mark Gillis

Follow on Twitter LinkedIn

Principal Consultant

Favourite topics – Performance Tuning, BLU acceleration, Flying, Martial Arts & Cooking
Mark, our kilt-wearing, karate-kicking DB2 expert has been in IT for 30+years (started very young!) and using DB2 for 20+. He has worked on multi-terabyte international data warehouses and single-user application databases, and most enterprise solutions in between. During his career Mark has adopted roles outside of the conventional DBA spectrum; such as designing reporting suites for Public Sector users using ETL and BI tools to integrate DB2 and other RDMS data. He has worked extensively in the UK, but also in Europe and Australia, in diverse industry sectors such as Banking, Retail, Insurance, Petro-Chemicals, Public Sector and Airlines.

Mark's Articles

Do the Needful

Published July 19th, 2017 - by

So the last few blogs have been a bit negative and have been built around common expressions and assumptions that make my hackles rise (If it ain’t broke, don’t fix it, We’re Risk Averse and Best Practice). Now this is the blog with the positive spin, so it might seem strange that I’m hanging it Continue Reading

Best Practice

Published May 12th, 2017 - by

OK, I bent the truth slightly. Lied, if you like. Mis-spoke if you’re a politician. I was going to go for a positive spin this time, but I’ve got one more grumpy negative subject to get off my chest first. And this one is going to be harder to justify. If it ain’t broke, don’t Continue Reading

In-Line Optimization with V11.1

Published April 7th, 2017 - by

Sometimes you might find that the Optimizer has chosen an access path with which you don’t concur. It’s not that likely, as the DB2 Optimizer is one of the most sophisticated of its ilk, but it’s possible that you may know something that the optimizer doesn’t: if, for instance, a table has just had some Continue Reading

We’re Risk Averse

Published March 3rd, 2017 - by

Find the latest blog, Best Practice.  I’m in danger of sounding like an episode of Grumpy Old Men, but this is another of those expressions that grates a bit for a database support consultant. In my previous blog (If it ain’t broke, don’t fix it) I mentioned one expression that stores up problems in the Continue Reading

If it ain’t broke, don’t fix it

Published January 31st, 2017 - by

Ever heard this expression? One of my least favourites. Flip it over and express it the other way around: Wait until it breaks and then try and fix it I don’t think that is something you seriously want to consider in a Production environment and yet it is something we come across as database support Continue Reading

Next Page »

Tag Archives