The first T-SQL Tuesday of 2019 is hosted by Garry Bargsley (@gbargsley), and the topic is “Automate All the Things“. Garry wants to know what this phrase means to each of us. What do we want to automate? What is our go-to technology for automation? To me, this was super easy. Surprise, surprise! It’s Biml, of course :) Since this post is part of T-SQL Tuesday, I wanted to go back to the basics and write about how you can generate SQL using Biml. But first, a little bit of background for those who are not that familiar with Biml.Continue reading →
T-SQL Tuesday #101 is hosted by Jens Vestergaard (@vestergaardj), and the topic is The Essential SQL Server Tools in my stack. There are several tools that I use every single day, such as Notepad++, Redgate SQL Prompt, and BimlExpress. In fact, there are so many amazing tools out there for data professionals that I created an entire session focusing on Tools and Tips For Data Warehouse Developers! Since I have already covered my favorite tools in other blog posts, I want to take a slightly different approach this time and share some of my favorite online tools.
T-SQL Tuesday #99 is hosted by Aaron Bertrand (@AaronBertrand) and the topic is Dealer’s Choice. What does that mean? Aaron wanted us to choose between two topics: write about something we are passionate about outside the SQL Server community, or write about T-SQL bad habits and best practices. I’m too afraid to argue with Aaron about T-SQL, so I chose the first option ;)
But what did I want to write about? Truth be told, I’m pretty boring. I don’t have any real hobbies outside of tech, just a few interests. I first considered writing about hiking. I need to disconnect completely once in a while, and my favorite way of doing that is to get sweaty while walking for hours up a mountain or waterfall. My Instagram (@cathrinesqueee) is my highlight reel, full of pictures and happy memories from my trips.
Some of my favorite hiking memories are: descending into Thrihnukagigur Volcano, eating lunch on top of the Rocky Mountains, relaxing at the Alluvial Fan, exploring the Garden of the Gods, climbing Seven Falls, overlooking the Norwegian fjords, driving across the never-ending Jotunheimen mountains, watching the fog roll in over Trollstigen, hiking Dinosaur Ridge, crossing the Capilano Suspension Bridge, taking a break on Mount Falcon, visiting the Loveland Pass, and gazing at presidents at Mount Rushmore.
However, instead of embedding all the pictures that are already on Instagram, I decided to write about something completely different. Something obscure. Something fun and geeky from way before I got involved in the SQL Server community. Something from my good old teenage fangirling days…
T-SQL Tuesday #97 is hosted by Mala Mahadevan (@sqlmal), and the topic is Setting Learning Goals for 2018. Mala wants to know what we want to learn, how and when we want to learn, and how we plan to improve on what we have learned.
It’s always hard to predict what I need to learn in an upcoming year, but 2018 is particularly difficult to predict. Why? Because at the time I’m writing this, I currently don’t have a job :) I finished my previous job last week, and I’m taking the rest of December off. Then in January, a new adventure awaits. I just don’t know what yet! So in this post, I’ll focus on some wants instead. I have picked three main goals: one technical, one personal, and one professional.
I will revisit this post next December and see how things turned out. It will be interesting! :)
T-SQL Tuesday #68 is hosted by Andy Yun (@SQLBek). Many SQL Server defaults are not ideal, and most of us have a list of defaults we always change. Andy wants us to Just Say No to Defaults and blog about what, why or how we change defaults.
If you are an SSIS developer like me, there is a big chance that the ProtectionLevel in SSIS Packages is on top of your list of defaults to change. The default ProtectionLevel is EncryptSensitiveWithUserKey (ugh), but most of the time it is not the best option. Raise your hand if you have ever asked your favorite search engine for advice on issues like “SSIS package fails in SQL Server Agent job” or if you have ever heard someone exclaim “but it works on my machine!?” :)
There are many great blog posts about the different ProtectionLevels, why you probably want to change to DontSaveSensitive as your default, and how to use configurations and parameters instead of encrypted SSIS packages. I will not go into details about any of that in this post, but I will use ProtectionLevel as an example default property you want to change in many SSIS packages at the same time.
How do you batch update properties in existing SSIS packages? You probably don’t want to open up every single package and change them manually?