timjohnstone's picture


Skills: T-SQL

Career Summary:

Tim Johnstone is a MCSE Data Platform in SQL 2012 and has been working in the database industry since 1997.

His particular strengths are in database migration and upgrade, database server infrastructure, procedure development and procedure optimisation.

His various roles have involved experience in a huge range of clients worldwide, from small partnerships to large enterprises, covering Tier1 applications and multi-terrabyte databases.

A sample of the activities he has professional experience in include product architecture and development, project management, technical and user training, technical pre-sales, vendor selection, change control, requirements gathering, report and dashboard design, and of course all things technical in the SQL database engine.

Specialties: Performance Tuning, Migration

Current Roles:

SQL Technical Specialist

From the Blogs
Sep 29, 2015

Data Breaches and Insider Threats

I’ll sound a bit like Captain Obvious for bringing this up, but it’s important to remember that security encompasses a lot more than protecting sensitive data from the specter of outsider threats like hackers. Properly implemented security policies also account for threat-models that include insiders – or people within your organization....More
Sep 15, 2015

Setting Up Additional Checks to Ensure Regular Transaction Log Backups 1

There’s simply no way to overstate the importance of regular Transaction Log Backups. Not only do they help protect from disaster, but regular execution of T-Log backups on Full (and Bulk-Logged) Recovery databases helps keep thing “fit and trim”. Most of the time, setting up a Notification for when T-Log Backup Jobs fail is enough to let you know when something goes wrong....More
Sep 1, 2015

Stop Using INFORMATION_SCHEMA and SysObjects for Exists Checks 3

Code like this isn’t optimal: IF EXISTS(SELECT * FROM sys.objects WHERE name = N'TableToDrop' AND type = 'U')         DROP TABLE TableToDrop; GO Neither is this: IF EXISTS(SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'TableToDrop')         DROP TABLE TableToDrop; GO Yet, I see both of those used all of the time – over and over again. Even though it’s 2015.  ...More
SQL Server Pro Forums

Get answers to questions, share tips, and engage with the SQL Server community in our Forums.

Sponsored Introduction Continue on to (or wait seconds) ×