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

Why your data still can’t answer a simple question 

By

Every organization I talk to has the same problem dressed up in different clothes....

T-SQL Tuesday #197 Invitation – An impactful session or two from a conference

By

I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...

Did You Really Name That Default?

By

Ten years (and a couple jobs) ago, I wrote about naming default constraints to...

Read the latest Blogs

Forums

The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI

By Terry Jago

Comments posted to this topic are about the item The day-to-day pressures of a...

Daily aggregation of Azure Blob Storage by tier (created/tier-change/deleted)

By BOR15K

Hello all, I’m looking for advice on how to derive a daily snapshot table...

SQL 2017 to SQL 2025. Good to Go ?

By homebrew01

We need to replace our Windows server running SQL 2017. Any reason not to...

Visit the forum

Question of the Day

Using OPENJSON

I have some data in a table that looks like this:

BeerID BeerName    brewer               beerdescription
1      Becks       Interbrew            Beck's is a German-style pilsner beer 
2      Fat Tire    New Belgium          Toasty malt, gentle sweetness, flash of fresh hop bitterness.
3      Mac n Jacks Mac & Jack's Brewery This beer erupts with a floral, hoppy taste
4      Alaskan Amber Alaskan Brewing     Alaskan Brewing Amber Ale is an "alt" style beer
8      Kirin       Kirin Brewing         Kirin Ichiban is a Lager-type beer
If I run this, what is returned?
select t1.[key]
    from openjson((select t.* FROM Beer AS t for json path)) t1

See possible answers