This months invitation for T-SQL tuesday came from Reitse Eskens (B | L | T). The original invite can be found here. I know Reitse quite well. He lives in the same in country, I visited one of his user groups, congratulated him on getting an MVP award, volunteerd together with him on two activities this year. I hope to continue this also this (2024) year. His invite Reitse’s question to the SQL Family is to share what we have learned from failed projects.

This months invitation for T-SQL tuesday came from Kay Sauter (B | L | T) . The original invite can be found here. Kay knows a lot of all data related stuff. So he wondered to whom I would be gratefull about last year. Despite the knowledge on Data, his invitation is about who we should thank… Wow.. That is a lot, only looking back one year… Last year My year is a turbulent year.

This months invitation for T-SQL tuesday came from Gethyn Ellis (B | L | T) . Here original request is explained here. Gethyn made a flying start with this request. He was one week late. But, Steve Jones (@wayoutwest and Steve Jones | LinkedIn) has given him the opportunity to continue the Journey. The full request of what Gethyn wants to know from us is: What is the best piece of Career Advice you have ever received as a data professional?

This months invitation for T-SQL tuesday came from Glenn Berry (B | L | T) . His original request is explained here. ](https://glennsqlperformance.com/2020/05/05/t-sql-tuesday-126-foldinghome/) Glenn’s invite asks us to what we have done in response to Covid-19. I first needed to think very deep about that question… What I have done in response to Covid-19? Or what Covid-19 has done to me? While the last question was not part of Glenn’s question, I just wanted to answer that also.

Thanks Kevin Chant (b|t) for hosting this Tsql Tuesday. You make it hard for me to answer this one. Especially since it is my first official post for a TSQL Tuesday. As a Database Infrastructural engineer there are some behaviors which you want to change. I am focused on security and ease of working I do not have many fantasies on SQL Server, but some improvements on the normal components would be nice to have.