As a consultant, I spend a lot of time with customers whose most significant pain point is what they’re spending on SQL Server licensing. In general, they’re all facing a similar scenario: they’ve found an architecture that works for them and as they scale that out for new clients or new users they continue purchasing the same servers (with the same version and edition of SQL Server) that’s always worked. While there’s nothing wrong with that, eventually management starts asking some questions:
- Why do we need all these servers when IT says they’re barely using any CPU?
- What do all these servers do?
- Why we are using X-year-old software?
As DBAs (especially those of us who wear the architect hat as well), we’re in a constant battle between priorities 1 and 1A: ensuring maximum uptime for our customers and spending the least amount of money to achieve that uptime. Settling for an older architecture on an old version of SQL Server does a great job fulfilling priority 1 but, generally, a poor job fulfilling priority 1A. The more money we spend on licensing, the less we have to spend on training, new hardware, etc.
It’s incumbent on us to keep abreast of the evolution in the SQL Server universe. As we’ve seen, Microsoft has massively accelerated the pace of their development in the SQL Server space, whether we’re talking about the database engine itself or Azure SQL Database or something in-between.
Can your company save money and provide required uptime by a move to Azure? Do you need to upgrade to SQL Server 2016 SP1 but downgrade to Standard now that in-memory OLTP, advanced compression, and greater partitioning functionality no longer require Enterprise Edition? Do you need to use something like ScaleArc to ensure you’re leveraging your complete Always On availability group investment?
This blog would be thousands of words long if I delved into every single option, but my point is a simple one. As things in the SQL Server universe change by the month rather than by the year, we all need to keep up with the latest developments and think about how they might make our job easier and/or our architecture less expensive to license and maintain so our company can spend more money on their most valuable resource – us!
Read blogs, follow SQL Server experts on Twitter, attend SQL Saturdays, and make plans to attend PASS Summit so you can stay on the cutting edge of cost-saving developments. If regular operations and maintenance keep you from having the time to reevaluate your architecture, engage a Microsoft data platform consultant (like me!) to help you in that evolution. We all know old habits die hard, but they can cost you and your company valuable resources as well. Engage with the community to help break out of those old habits (and learn cool things too)!
I generally use this blog to let people know about community events where I’m speaking, pass along Microsoft Data Platform-related technical information I’ve found useful, or to participate in T-SQL Tuesday blog parties. For the next few days, however, this blog is going to be home to my updates from my racing debut at Indianapolis Motor Speedway. I’m driving in the Open Wheel World Challenge this weekend and, honestly, I lack the words to describe how cool this is.
Every racing driver (or at least every one that grew up in the Midwest of the United States) dreamed of crossing that yard of bricks in any car. The fact that I am able to run at Indy this weekend, in my own car, with family and good friends supporting me is honestly hard to believe. Hopefully we have a good, clean weekend.
After this Sunday, I plan to revert to more disciplined technical blogging. For the next few days, though, I will update this blog with racing updates as often as I am able. If you’d prefer to follow along on Instagram, please search the hashtags #jaygoracing and #sqlatspeed. Talk to you from the track!
Usually my view of Atlanta is quite similar to the image above – as a Delta Medallion member and frequent traveler I see the airport in Atlanta quite a bit. That said, I’m thrilled to announce that I’ll be speaking at SQL Saturday 652 in Atlanta on Saturday, July 15. If you haven’t registered, they’re getting closer and closer to capacity so please register here before it’s too late!
I’m looking forward to ramping up my blogging next month, but the current priority is prepping my race car for its debut at the Indianapolis Motor Speedway in a little over two weeks at the Open Wheel World Challenge. Please forgive the brevity of this blog, but rest assured both the technical and racing content on this blog will ramp up quite a bit in the next several weeks. For now, go register for SQL Saturday Atlanta if you’re in the area and I hope to see you either there or at Indy!
Unfortunately, I haven’t had the opportunity to talk racing very much on the blog here, but hopefully that is about to change. My Formula First (in the image) had its engine delivered to Autowerks in New Jersey for rebuilding before the 2017 season.
More excitingly, my 2017 season begins at the Indianapolis Motor Speedway (yes, I bolded it – it’s just that exciting) with the Open Wheel World Challenge. When I get my engine back later this spring I look forward to blogging about its re-installation in the car and our preparations for an event that will be, at minimum, something 9-year-old me would have never believed. I’ll be racing at Indy this summer! To be continued…
Last Saturday (8/6/16) I had the pleasure of doing my first community presentation at SQL Saturday 531 in Louisville, KY. During a great speakers’ dinner Friday night at Brick House Tavern + Tap I had the opportunity to meet a few members of the #sqlfamily and get some solid advice for my rookie presentation the next day.
My presentation the next day went fairly smoothly despite a visit from the demo demons (courtesy of what seemed to be a flaky system hooked up to the projector) that deprived my session of some of the demos I intended to present. I genuinely appreciated each and every person that attended the session and I hope the Always On tips and tricks I shared are or will be a help to their organizations.
In short, if you’re not attending SQL Saturdays, why not? It’s tons of free training from experienced people and you’ll meet good people as well. And, if you’ve attended a few SQL Saturdays (as I have) and have tips and information to share, why not try your hand at presenting? It was a rewarding, invigorating experience and I can’t wait to present again in the near future.
If I still haven’t convinced you to involve yourself in SQL Saturdays, check out Chris Yates’ blog for a great breakdown of why SQL Saturdays can be one of the best investments you can make in your career.