I spent most of July 1st relaxing in the sun, reading The Hitchhiker’s Guide to the Galaxy and enjoying my vacation. I spent the rest of July 1st reading, re-reading and re-re-reading the e-mail I received from Microsoft congratulating me with my first MVP Award.
Unfortunately my copy of The Hitchhiker’s Guide to the Galaxy did not have Don’t Panic written in large, friendly letters on the cover. So I panicked a little. I think I may have panicked more than just a little. Actually, I’m pretty sure I panicked a lot.
You see, I had mixed feelings about becoming an MVP. I am truly honored and thankful, but it is also very intimidating to be part of a group with so many talented people that I admire. I don’t have decades of experience, I’m not a SQL Server expert, I haven’t published any books and I haven’t created any scripts that are used all over the world. Why should I deserve to become an MVP? I panicked a little (or a lot) because I compared myself to those who are years ahead of me down the road, and because it felt like I cut in line in front of amazing people who deserves the award more than me.
So I took a step back and thought about what the MVP Award means to me. To quote Microsoft: MVPs are community leaders who’ve demonstrated an exemplary commitment to helping others get the most out of their experience with Microsoft technologies. They share their exceptional passion, real-world knowledge, and technical expertise with the community and with Microsoft."
To me, it’s all about community. I may not be the most experienced SQL Server expert, but I helped restart SQL Server User Group Norway. I was the main organizer of the first SQLSaturday in Oslo and currently organizing the second one. I’ve volunteered and presented sessions online, in Europe and in the US. I blog, I tweet and I do my best to help others.
And I love it. Being recognized by Microsoft and getting a thank you for what I have done this past year means so much to me. Thank you to everyone who has been there for me and believed in me, it means more to me than I can say. Receiving the MVP Award inspires me even more to give back and pay it forward, to keep learning and sharing my knowledge, to help grow the Norwegian SQL Server community.
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?
One of the main tasks in Biml projects is to import source metadata. The recommended method is GetDatabaseSchema. This method returns an ImportResults object that contains SchemaNodes (schema metadata) and TableNodes (table and view metadata).
Hello, my name is Cathrine, and I am a tab hoarder 🤓 I always have lots of tabs open in SQL Server Management Studio (SSMS) connected to different environments. I have written about how Redgate SQL Prompt Tab Coloring makes it easy to find the right tab(s) based on the tab color, but that is not the only tab feature that saves me a lot of time.
Redgate SQL Prompt Tab History. is amazing! It allows you to view and reopen closed tabs, even those unnamed and unsaved tabs with ad-hoc queries that you thought you would never need again. It also allows you to quickly navigate and search through closed and open tabs.