T-SQL Tuesday #145: The Pandemic, Costa Rica, and Events

by Xavier Comments: 6

Welcome back to this blog party tradition that has been going strong for years!

I am really happy to be hosting this month and since we are in the middle-ish (hopefully closer to the end) of a pandemic, I would like to ask you the following question:

How much do you love meeting in person, where would you like for your next event to take place, and why Costa Rica?

I am no stranger to in-person events. In fact, I’ve spent a good deal of my life traveling all over the world, teaching technologists from all kinds of companies – big and small – on a wide range of subjects.

Some of the places I have traveled are fantastic for that real-world interaction that we all need.

Yes, remote work is nice and many companies and employees have indeed found out that you can actually work from home in an efficient manner.

However, IMHO, there is no replacement for that feeling of walking into the presentation hall, having the chance to talk to experts and meet new and interesting people that are most likely having the same problems as you, or that are trying to change the world one application/solution at a time.

Now, help me by answering these questions:

  1. Which is your favorite conference and why?
  2. Which is the best venue that you have visited for a tech conference?
  3. Who is the best presenter that you have ever listened to?
  4. Which location would you like for your next event to take place and why Costa Rica?

Let me know what you think!

The Rules:

  • Write your post and publish it on Dec 14 ,2021
  • Include the T-SQL Tuesday logo and link to this post.
  • Ensure you leave a comment on this post with the URL of your post (or a trackback/pingback)
  • Publicize your  post on Twitter/LinkedIn with the #tsql2sday hashtag

Implementing Search Article on MSDN

by Xavier Comments: 0

A couple of years ago I wrote an article for MSDN magazine called Implementing Your Own Enterprise Search.

I was really excited as I started my career as a .NET developer and MSDN magazine was the last word and cutting-edge on .NET at the time.

I remember waiting for each new dead-trees edition magazine to arrive so I could read it cover to cover and learn as much as I can.

Well, mostly thanks to Julie Lerman, I was able to write one article as she pointed me in the right direction to submit an idea.

One thing that’s missing is the source code as MSDN Magazine is no longer maintained so I created a repo for it:


Hope it helps!

How Pluralsight Changed My Life Twice

by Xavier Comments: 1

“Skills speak louder than words”

Indeed they do, but the “actions” part is step 2 once you get “skills”.

This is the story of how skills + actions with @pluralsight changed my life TWICE.

Let me tell you why

I’ve been in training since around 2002, when I co-created and delivered the 32-bit to 64-bit migration labs for @Microsoft, @HP, and @Intel while working at Artinsoft.

We were teaching enterprises all over the world how to migrate their code from 32-bit processors to 64-bit. This was part of an initiative led by Microsoft and since Artinsoft created the VB6 to VB.NET migration assistant, we got a chance to help companies worldwide migrate their code.

The effort was called Route 64, and we got a chance to train companies of all sizes while traveling the world (the travel part was fun, check out a list here: https://www.xaviermorera.com/road-warrior/) .

Windows 7: 64-bit or 32-bit? Memory and performance | 4sysops

One of the locations where we gave our trainings was Building 20 in Microsoft’s main headquarters in Washington.

At the time, there was a small company giving trainings in Building 20 as well. Who knows, maybe I even crossed paths with some of its founders back then.

At the time, Pluralsight was instructor-led training–the online part had not been born yet. A few years later, it did and that’s when my life started changing.

I became a subscriber and started working on my skills, which helped me become a better programmer and engineer.

This was life-changing moment #1 for me.

My skills improved and I kept getting better at what I did which also allowed me to help some of my peers one-on-one whenever they are stuck in their work (something I still do and enjoy today).

One day I had an idea, what if the things I am teaching and helping my peers with… what if… I create video trainings that I can then share?

So I sent this mail in their ticketing system.

They replied a month or so later and I started my auditioning process to become a Pluralsight author.

This was life-changing moment #2.

I got accepted and started working nights and weekends creating trainings until I was able to fire myself from my day job and dedicate myself to work on my passion… creating trainings!


And so Big Data Inc was born… (story to be continued)

Working with Large Files in GIT (LFS)

by Xavier Comments: 0

The other day I casually committed a file and when I pused to git I ran into an error letting me know that I was hitting a limit, I exceeded the allowed file size in Git which is 100 MB.

This issue is quite well documented in several places, including this issue in Github: https://github.com/desktop/desktop/issues/4066

Yeah… who commits a file over 100 MB in size in Git.

Guilty as charged… it was a template (potx) that I needed to apply but that had pleeeeeenty of images.

How do I fix this and commit a large file?

#1 First, I need to “uncommit” the file which is easy since I have not pushed it yet (obviously). so a git reset works

#2 Use LFS, Git’s Large File Storage, which is an open source Git extension for versioning large files.

Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.

It is easy to use, simply install it first. You can download from https://git-lfs.github.com/

Then you need to install in your account by running (this needs to be done only once per account)

git lfs install

Next up, specify which files you want to track, that is store, in LFS (needs to be done by repo)

git lfs track "*.pptx"

Repeat for each file type that you intend to store in LFS. This information is stored in a file called .gitattributes.

Finally, commit this file so that anyone that pulls the repo also uses LFS (they need to install it too)

Work normally.

For any files that you committed before LFS, you need to migrate them.


PS: If you want to learn more, I have an entire course on how to use Git with a GUI