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?
T-SQL Tuesday #66 was hosted by me on May 12th. The topic of the month was Monitoring. We all monitor something while working with SQL Server, and this month’s blog posts covers all kinds of topics by DBAs, developers and BI professionals.
Monitoring is a very wide, but also very important topic for all of us. Be proactive and monitor your databases, servers and environments (even test and development), and make it a goal to discover issues before your end users alert you. Invest in vendor solutions, use the tools available in SQL Server or write your own custom solutions, just make sure you monitor what is critical in your company. Capture data to see trends over time and use PowerShell to automate tasks. Also don’t forget to monitor the monitoring solutions!
Want to participate or read more?
Monitor the #tsql2sday hastag on Twitter the first week each month for the invitations. Steve Jones (@way0utwest) keeps an updated list of all previous T-SQL Tuesday Topics. If you ever need inspiration to write a blog post, just pick a topic and write away.
Thank you again to everyone who participated in T-SQL Tuesday #66! :)
T-SQL Tuesday #66 is hosted by me (yay, fun!) and is all about monitoring. We all monitor something while working with SQL Server, and there are so many topics to choose from. As a Data Warehouse developer I use Adam Machanic’s sp_WhoIsActive all the time, I look at the Integration Services Dashboard in SSMS to monitor SSIS package executions and I check the Job Activity Monitor for a quick overview of what’s currently running on our servers.
However, I decided to write about a custom Real Time Monitoring solution we use in my company (Storebrand) that my coworkers in Lithuania created. I couldn’t resist this opportunity to show one of our cool solutions that I get to use and to brag about how talented my coworkers are :)
Storebrand Real Time Monitoring
There are many great monitoring solutions available out there. In my department we actually use several solutions from vendors to monitor our SQL Servers and Business Intelligence environments, but we also had some very specific monitoring requirements. None of the vendor solutions available at the time were able to provide all the functionality we needed, so we built a custom real time monitoring solution:
Easily create and edit personal projects, or collaborate on shared projects
Web-based interface to access projects from any computer in the network
Pick and choose specific files, databases, cubes, jobs and even job steps to monitor in each project
Create status and quality checks, and subscribe to get alerts via e-mail or SMS if the checks fail
Welcome to T-SQL Tuesday #66! My name is Cathrine Wilhelmsen (@cathrinew) and I’m very happy to be your host for the T-SQL Tuesday coming up on May 12th.
Much Monitoring in the Month of May
The topic of the month is monitoring. We all monitor something while working with SQL Server: Maybe you’re a DBA who monitors database performance, an SSIS developer who monitors job and package execution, an application developer who monitors queries or a BI analyst who monitors report usage? Do you use T-SQL or PowerShell scripts? Have you created your own monitoring reports or applications? Have you invested in a complete monitoring solution from a vendor? What is monitored manually and what is automated with alerts? If a brand new SQL Server professional in your role asks you for advice, what do you say is the number one most important thing to monitor? Have you ever stayed awake for a week solving a problem that could have been avoided with proper monitoring? Did you implement a monitoring solution that saved your company?
Be creative! There are so many topics to choose from, and you can of course write about anything you want as long as it is related to SQL Server and monitoring. It doesn’t matter if you’re new to SQL Server or have decades of experience, whether your blog post is short or long, an introduction or a deep dive, if you include scripts or screen shots… Just join the party and have fun while you share your knowledge. (And if you joined the #SQLNewBlogger challenge in April, this is a great way to keep blogging!)
What is this T-SQL Tuesday thing?
T-SQL Tuesday is a monthly blog party started by Adam Machanic (@AdamMachanic) back in 2009. The concept is simple: The host of the month picks a SQL-related topic and writes an invitation on the first Tuesday of the month. All bloggers are welcome to join in, they have one week to write a blog post about the chosen topic and publish their post on the second Tuesday of the month. The host then writes a summary of all the participating blog posts.