HuggyBear

Born and raised in Vancouver, Canada, with a brief excursion to study in Brussels, Melbourne & Washington D.C., Hugo has been working with SQL Server since 1998. He’s busied himself as a DBA since 1999 (with mcdba & mcitp certifications in ‘01 & ‘08 respectively), as independent consultant with his own company, Intellabase Solutions, since 2002 (now part time), and has held various permanent position with Transcontinental, Sun Life Canada, and now Alithya as a consultant. He enjoys writing documentation for quick, safe infrastructure rebuilds and expansions, and most challengingly, propositions to Executives Management on how to improve enterprise Security. He has spoken at SQLteach/DevTeach, Montreal Dot Net User Group, SQLGulf, Vermont User Groups over 5 times, has a blog on SQLServerCentral, and has been recognised as a SQL Server MVP in 2010.
Recently has adapted thanks to certification and experience the Data Engineering age, meanwhile studying the latest improved scripting language, Python.
  • Interests: Lately (2019): windfoiling or windsurfing with a Skroka foil....amongst many other supposedly 'extreme' sports, but which are really just the norm for people raised in Lotusland aka Vancouver, BC, lower-mainland region, Sea-to-Sky country as we know it.
  • Blog: http://dbhive.blogspot.com/
  • Jobs: SQL DBA, Data Engineer, Migrator, Clusterer, Security Implementor

Technical Article

Querying the Procedural Cache on Canada Day (July 1st)

The goal of this post is to understand the procedure cache and execution plans to ensure we use fewer resources and that queries run better. Better means higher throughput, more concurrency and fewer resources – as described by MVP Joe Webb during SQLTeach in Vancouver just last month.

You rated this post out of 5. Change rating

2009-07-08

1,134 reads

Technical Article

Configuring Auto-Retry on SQL Server Agent

The goal of this post is to explain how to take advantage of Auto-Retry and why you will want to use it. I hope to clarify in which circumstances an auto-retry works best and when not to use it also. The (disclaimer!) point is that every job has its own constraints, requirements, and has to be evaluated individually for whether an auto-retry will work. I will try and keep this summary short and crisp, but still with enough detail to understand auto retry best.

You rated this post out of 5. Change rating

2009-06-01

3,877 reads

Blogs

How AgentDBA Identifies Backup Failures

By

Every DBA has a box like this. Sitting untouched for months. Nobody’s proud of...

Tip: Expanding a SQL statement

By

In all recent versions of the database you can call DBMS_UTILITY.EXPAND_SQL_TEXT to get the...

AI Helps Me with My Sloppiness

By

I type fairly well. Well, I type fast, but I do wear out a...

Read the latest Blogs

Forums

From SQL Server On-Premises to Claude Desktop: How I built a Full MCP Pipeline

By Cláudio Tereso

Comments posted to this topic are about the item From SQL Server On-Premises to...

Independence Day 2026

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Independence Day 2026

Independence Day 2026

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Independence Day 2026

Visit the forum

Question of the Day

Independence Day 2026

In the original Independence Day movie (1996), what type of computer did Jeff Goldblum use to connect to the alien mainframe? Take a guess, don't look it up or ask AI.

See possible answers