I'm a constant learner. I try to regularly experiment and try new things at work and in the rest of my life. For work, sometimes this means working outside of the other hours and commitments I have to get better at manipulating data. Sometimes I go deep and sometimes I just want the general gist of how to solve a problem I'm having. Time constraints come into play at times because there's never enough. Even with limited time, I do want to understand the reasons why things work, or why I should make a choice for some function/method/framework/pattern/etc.
I've been working with R a bit this summer, trying to learn a bit more. I've tried tryr.codeschool.com as a guided tour, but sometimes it doesn't help me understand enough of the details. Even as I experiment, I'm going through the motions. I purchased R in a Nutshell, and just got Stephanie Locke's Working with R. I'm hoping these books will give me a more thorough grounding in R.
As I'm learning, I always want to ensure I understand the implications of how I may write scripts. What do my choices mean for quality, performance, etc. Sometimes trying to understand why slows me down, and I don't get much done. That's fine, and maybe that's for the better. However, I don't want to learn slowly by going through all the pain that someone else went through. I want to know how someone would write code today, and why they do so.
I ran across this post on learning the hard way. It discusses the way some people try to teach others, and I've been through some of this as I've tried to learn various technologies. The teacher sometimes wants to assume I am going through their pain and can sympathize, but often I'm learning something new for the first time. I'm sure I've been guilty of this as well, perhaps trying to level set or show an old (or poor) practice to emphasize why it's better to write code in a new way.
The thing is that my time is precious, and I shouldn't have to work through the mess of the way things used to work to build good habits today. What's new to someone might not be new to all, and certainly at some point, all code isn't new anymore. I'd rather teachers, and me, sometimes focus on giving us good habits today. Teach us the right way now, and spend time on error handling, testing, or other good habits. Certainly there are cases where we need to know about the changes to systems, but explain this is an upgrade section. And then tell me what's different, don't wax nostalgic on the way you once were forced to find innovative solutions.
The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music.
The industry standard for comparing and deploying SQL Server database schemas
Trusted by 71% of Fortune 100 companies, SQL Compare is the fastest way to compare changes, and create and deploy error-free scripts in minutes. Plus you can easily find and fix errors caused by database differences. Download your free trial
How mature are your database DevOps processes?
Complete Redgate’s Database DevOps Maturity Assessment to understand how mature your processes are, how you compare against your peers, and receive recommendations for improvements. Take the assessment
SQL Server Auditing is a powerful out-of-the box toolset that captures auditing information and writes to a file or the Event Log. This article examines the little things that might snag you up. More »
There are several obvious problems with poor SQL Coding habits. It can make code difficult to maintain, or can confuse your team colleagues. It can make refactoring a chore or make testing difficult. The most serious problem is poor performance. You can write SQL that looks beautiful but performs sluggishly, or interferes with other threads. A busy database developer adopts good habits so as to avoid staring at execution plans. Rob Sheldon gives some examples. More »
Today I ran into something on a client server I unfortunately see too often. The DBA goes through the trouble... More »
Question of the Day
Today's Question (by Avinash):
When columns with different datatypes are compared in SQL joins or if we assign variables of one datatype with variables of other datatype, then SQL server implicitly converts datatype based on their precedence. If value can't be converted SQL will generate data type conversion error. What will be the output datatype from this code:
SET @txt = '2017-01-01';
SET @dt = '2001-01-01';
SELECT result = @dt + @txt
Think you know the answer? Click here, and find out if you are right.
We keep track of your score to give you bragging rights against your peers.
This question is worth
1 point in this category: Data Types.
We'd love to give you credit for your own question and answer.
To submit a QOTD, simply log in to the
This book shows how to deliver eye-catching Business Intelligence with Microsoft Power BI Desktop. You can now take data from virtually any source and use it to produce stunning dashboards and compelling reports that will seize your audience’s attention. Slice and dice the data with remarkable ease then add metrics and KPIs to project the insights that create your competitive advantage.
Yesterday's Question of the Day
(by Steve Jones):
I want to store Marvel data. My goal is to store a character name, a movie title, and a year of release. Which construct in R creates a data frame?
This is a simple little script, but may come in handy for some. During our database upgrades we always run a series of utility steps to make sure our code is in sync and functioning properly based on the revisions that have been made for each release. This script is one of those run to recompile all views to catch any "SELECT *" views, or views where the underlying schema has changed and we missed changing the view.
This can be added as one of your steps to your deployment SQL.
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.