First at all, I would like to start this simple blog saying: Thank you everyone who was part of this marvelous adventure, my wife who support me in an exceptional way from the beginning, especially encourage me to do a step forward, you know how much I love you Lauren , and thanks to my kids (Octi and Giovanna) for their patience and understand that Dad needed a little of time for preparing the presentation.

This is the second article of a series dedicated to implementing Recursive Common Table Expression in different kind of scenarios, and this time I will address another use case; it basically consists in filling gaps inside a sequence of an incomplete range of dates.  I would like to comment that the next example has been taken from MSDN forum, I have chosen because I think it is an excellent way to prove how versatile the recursive CTE is, the most creative solution was proposed by Peter Larsson (swePeso) and he brought us  a valid and optimal implementation which is useful since SQL Server 2005 and up versions.

I remember the first time that I discovered the amazing feature called Common Table Expression (CTE), it was during my first read of Itzik Ben-Gan book (T-SQL Querying), maybe one of the most interesting feature together with Windows Functions.  I know, I am a declared fan of CTE, but we can start defining a CTE as a sort of temporary result set and which exists only during the lifetime of the query.

Continue reading

The stereotypes are an “easy” and “toxic” way of grouping and split the people, we can find it in every society and it is extended to the professions.  The IT field it is not the exception, in fact, the IT workers profile don’t fit in many of classic “supposed to be” and being realistic, the stereotype is so far to be true, you should read this interesting article in the Wall Street Journal titled “Profile of an IT Worker” (https://www.wsj.com/articles/profile-of-an-it-worker-1382128556).