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

All authors

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

All authors

Blogs

T-SQL Tuesday #192: What career risks have you taken?

By

This T-SQL Tuesday is hosted by the one and only James Serra – literally...

T-SQL Tuesday #196: Taking Risks

By

This month we have a new host, James Serra. I’ve been trying to find...

The First Steps: Understanding the Basics of FinOps

By

As a DevOps professional, I’ve seen firsthand how cloud costs can quickly spiral out...

Read the latest Blogs

Forums

would it be so terrible to install ssms on a few user desktops?

By stan

Hi, ssms is free here.   I can think of other reasons to do this...

I'm thinking about submitting some articles

By Doctor Who 2

I've written some documentation on using different Markdown types of files on GitHub. It's...

Not Just an Upgrade

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Not Just an Upgrade

Visit the forum

Question of the Day

Restoring On Top I

I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens? 

USE Master
BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO

USE DNRTest
GO
CREATE TABLE MyTest(myid INT)
GO
USE master
RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACE

See possible answers