SQL University is one of the greatest concepts I’ve seen in the SQL Community. Thanks to Jorge Segarra (Blog | Twitter)for coming up with it and organizing it. Today we are going to talk about something dear and close to the concept of SQL University. Blogging! Blogs are an important part of the concept of SQL University. With them we can easily bring this wealth of knowledge in the course syllabus format with writers from the SQL Community in a vast geographical range and range of expertise.
Getting your day-to-day experiences and knowledge out to the community can be tough sometimes. We can share what we know and what we learn with the teams we work in, but the walls of our building keep that from going far. Blogging removes the wall and much does much more for our personal growth.
Promoting and sharing blogs doesn’t only bring with it satisfaction of sharing what you’ve learned but also allows you to help everyone in the community so we can all build our knowledge base.
My own personal story of blogging
I wrote my first blog in November of 2008. The title was, “User to Schema to Roles for controlling security”. I won’t lie; I have learned an enormous amount about how to blog since then. I’ve learned more about writing period! Writing is an art form and catching the audience’s attention is important when you write your blogs. The best part of blogging and writing in general is that everyone has their own way of getting the audience’s attention with humor, technical skills and just downright talent. You hold that talent inside you, but you need to try it to find it and build on it.
In the SQL Community, we have hundreds (if not thousands) of bloggers out there writing daily and providing step-by-step articles that help us learn new things, fix old things and become better DBA’s all around. So why write your own if the wealth of knowledge exists and is still pouring out of all of these SQL Community members?
If it is written already, I don’t need to write it. <– Horrible statement!
The one reason I can give you to not hold back on starting up your own blog and sharing your SQL Server trials is: everyone sees a situation differently and replays that situation to an audience in many different ways. Your way (yes, yours) can be the way that a hundred people grasp while other perspectives leave them with questions. That reason alone takes, “it’s already done” and throws it down the truncate statement. (Haha! SQL nerd humor is awesome!)
Let people review them
Letting your guard down and sending your drafted blogs to friends and peers in the SQL Community can be hard. No one likes to be marked by a red pen or be told that the entire blog may need a new direction. In some cases, technical reviews find errors and mistakes all over the entire process and even directions describing why what you are telling everyone might not be the best way to do it.
A perfect example is a blog on using TRUNCATE_ONLY. SHRINK and TRUNCATE_ONLY are just bad. (Paul Randal (Blog | Twitter) says so.) Very bad! Google TRUNCATE_ONLY log and you will find plenty of bad advice, unfortunately. The use of this option and action is really not a good thing to do on your SQL Servers. We do see a lot of blogs going out on the topic though, and complete step-by-step instructions on how to do it. If these blogs were placed under a technical review, the author may have gotten this reply:
“Ted, I hate to say it but the blogs needs a lot of help in the technical realm. Your steps are perfect and solid for anyone to take and get a shrinkfile working. No doubt about that! The problem is, you don’t say anything about why shrinkfile is not good and when to use it. Just says: do it! I could see how that might lead to a DBA putting a shrinkfile (or database) into a job and running it endlessly. I would definitely add a description of the action and emergencies where it really is only called on.”
I can also honestly say that most of the SQL Community and bloggers we have would be polite and respectful in while doing a review like this.
Practice if you are unsure
Are you still unsure about blogging? Practice a few blogs. Write them and save them in a lost sea of folders in your Documents. When you do that, keep your eyes and ears open in the community. I can pretty much guarantee you that at some point, someone is going to mention the situation you wrote about either happened to them or they need help on it. Then scramble to get your blog up and give it to them!
Which blogs should I read?
There are leaders in the SQL Community and those leaders all actively blog (and blog a lot). The list could go on forever if we put them into this lesson, but luckily enough we have PASS to the rescue as always. PASS collected a list of community bloggers and posted it.
Still not convinced?
Mike Walsh contributes a lot to the SQL Community. A little while ago Mike spent the time writing a series on blogging. The blog series starts with a video chat session with Brent Ozar on experiences with blogging. Then the series goes into, “Why I should blog”, “How should I blog” and the second part of the interview with Brent. The series is excellent and answers a lot of questions and pumps you up to get into blogging SQL Server and about the community. If I haven’t convinced you how blogging can be extremely gratifying, Mike will.
Thank you for taking the time to attend another SQL University course! Please take the time to fill out the SQL University Course Evaluation.