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

The #MS_DatabaseConnector## Role: #SQLNewBlogger

By

I had seen these roles in various instances, but never dug into the new...

Asking for Help Isn’t a Weakness

By

During COVID, I attended training on software/enterprise architecture given by Mark Richards. One of...

The Proof of the Backup Is in the Pudding

By

For me, the objective is straightforward: have a backup strategy that is reliable, understandable,...

Read the latest Blogs

Forums

Pay for Performance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pay for Performance, which is...

Layanan BCA KCU KUPANG (+62) 838-4945-0961

By layanan 24jam BCA

Wa:083849450961 Jl. Tompello No.23 A, Oetete, Kec. Oebobo, Kota Kupang, Nusa Tenggara Tim. 85119

Layanan BCA KCU PURWOKERTO (+62) 838-4945-0961

By Halo_BCA

Wa:083849450961 Jl. Jend. Sudirman No.391 A, Brubahan, Purwanegara, Kec. Purwokerto Tim., Kabupaten Banyumas, Jawa...

Visit the forum

Question of the Day

The ##MS_DatabaseConnector## User

On SQL Server 2025, I run this code as a sysadmin:

CREATE LOGIN Demo WITH PASSWORD = 'Demo1234567'
GO
ALTER SERVER ROLE ##MS_DatabaseConnector## ADD MEMBER Demo
GO
I then login as Demo and run this:
USE sandbox
go
SELECT CURRENT_USER
What is returned?

See possible answers