Voice of the DBA

Category: Editorial

  • #sqlhelp

    I know that Twitter is really representative of only a fraction of the people in the world, and arguably it’s not even a good representation of any group because it’s a self-selective group that chooses to share thoughts, ideas, news, etc. with the world. However I do enjoy the medium, and find myself learning about the world, thinking about opinions, and once in awhile, getting help.

    There is a hashtag on Twitter called #sqlhelp. It’s an amazing tool that I’d highly encourage all of you to consider when you want a quick answer to a problem. Hashtags are a way of denoting tweets about a common subject, though there is no official set of hashtags. You can make one up yourself and see if it catches on.

    #sqlhelp certainly did, and I find it useful for many short, quick questions. While I was writing this piece, I saw questions come up on licensing, Oracle->SQL Server conversions, security in a database, and how to read an execution plan. I also saw some noise, with requests for consultants to teach, product advertisements, and a webinar notice. I’m slightly worried that noise level might overwhelm this channel, but if you’re on twitter, you should try using it for your next problem.

    As with any answer you get from the Internet, you should test things yourself and decide how trustworthy the source is. You might get an answer from Brent Ozar or Paul Randal, but you might get some new DBA on his first day of work. Also be aware that 140 characters can severely limit the questions you can ask. If it’s complex, I’d suggest you try the SQLServerCentral forums instead.

    Whether you like Twitter (and #sqlhelp) or not, I do believe that this is a great example of how our community does a great job of helping each other out. We teach, learn, support, and inspire each other, arguably more than any other industry or technological group I know of. It’s a joy to be a part of the community, and I’d encourage you to join us on Twitter, forums, or local events.

    Steve Jones

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 3.3MB) podcast or subscribe to the feed at iTunes and Mevio . feed

    The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.

  • A True SQL OS

    Today’s editorial was originally published on Aug 26, 2009. It is being re-run as Steve is on vacation.

    I have heard a number of talks from SQL Server developers at Microsoft that refer to the internal SQL Server database engine as the “SQL OS,” since it almost exists as its own operating system from their perspective. Much of the development work these people have done in scheduling, threading, memory management and more, is reminiscent of the work done on operating systems. So it’s called the SQL OS.

    As SQL Server has grown wider and wider, incorporating more and more features, it almost seems to have all the features that might qualify it as its own operating system, but it still has dependencies on Windows, and exists as a service under Windows. That is both good and bad, since you can easily use your physical server for other applications, but those applications can take resources away from SQL Server and cause contention.

    Since it seems that many people make a practice of only installing SQL Server on a machine, it makes me think that we’re actually ready for a true SQL OS, one that is installed on a machine and has no other capabilities other than what is inside SQL Server.  I think this could be done today, perhaps using a specialized Server Core installation in Windows, and eliminate the possibility of anything interfering with SQL Server itself. We could still add it to a Windows host if needed, but we’d have the option of a specialized SQL box, maybe as an Enterprise feature.

    There could be some great advantages of going down this path. Windows I/O and scheduling could be tuned specifically for SQL Server, or just incorporated into the SQL Server platform. With VMs, you could still partition your hardware to have a SQL VM and another Windows VM for other applications. The new Filestream features could be extended to allow file operations to the SQL Server instance, and what’s more, we could then access and manipulate these files from within the server. Doing so in a separate file system is a constant challenge for many developers and DBAs.

    I don’t think this will happen for a few reasons, not the least of which is licensing. There’s a Windows and a SQL Server license for every instance, and I can’t see Microsoft wanting to sell less copies of Windows.

    However it’s nice to dream of a way to build a SQL Server platform that only requires DBAs.

    Steve Jones

    The Voice of the DBA Podcasts

    Everyday Jones

    The podcast feeds are available at sqlservercentral.mevio.com. Comments are definitely appreciated and wanted, and you can get feeds from there.

    You can also follow Steve Jones on Twitter:

    Overall RSS Feed: or now on iTunes!

    Today’s podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.

    I really appreciate and value feedback on the podcasts. Let us know what you like, don’t like, or even send in ideas for the show. If you’d like to comment, post something here. The boss will be sure to read it.

  • Developers, developers, developers

    StackOverflow ran a survey for their members in 2013 and released some results recently. The results are on their blog, along with some observations about the data. While most of this audience aren’t in the development space, some may be, and the impacts of the results could certainly affect our careers.
    Most developers and applications aren’t getting much accomplished without data, and whether they use SQL Server, another RDBMS, a NoSQL platform, or a dumb data store, chances are we can help them. Chances are also that if they make a poor decision, we’ll be dealing with the mess in some way.
    The observations note that mobile is still growing, and I believe that. I still think the mobile market will dwarf the PC explosion we’ve seen the last 20 years, and that means we should be preparing and understanding how to deal with data from mobile devices, think about scaling to meet lots of small, quick calls for data from a device.
    I also like the fact that more people are working remotely. If they let developers work remotely, that’s a good step towards DBAs becoming remote as well. As someone that has worked from home for over a decade, I appreciate the challenges, but I still can’t help but thing my productivity is much higher than it ever was in an office.
    It’s also nice that the second most popular language (in use) is SQL. Not necessarily T-SQL, as I’m sure various other platforms are developed on, but it does show that SQL is very important, even to developers. Perhaps the next time a developer is struggling with SQL, you can refer them to this survey and then see if you can help them improve their query skills.
    Steve Jones

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 2.4MB) podcast or subscribe to the feed at iTunes and Mevio . feed

    The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.

  • Continuous Delivery

    At Red Gate Software, we have a product called Deployment Manager. Its aim is to smooth and ease the process of deploying changes in your software from environment to environment, database and application code. What I like about the product isn’t that it makes the overall software development process easier, though it does. It’s that the team behind the product is using their own tool and technique to . They’re practicing Continuous Delivery (CD), even as they work to help make it easier for you to practice CD.

    That’s pretty neat. Even if you don’t want to release software that often, you have to admit that’s cool. I once worked at a company that released changes every week for well over a year, and I have to say that the development team was very proud of what we accomplished every week when the deployment was complete.

    However we didn’t release every change every week, and as the Deployment Manager team as learned, some things take longer than a week. There are particular challenges to handling the partial release of software, and while you can overcome lots of them, at times you have to delay a release. However, I’d much rather delay my release a week or two than months. The latter has happened in many places I’ve worked when a large application is being built.

    At Red Gate we do think that continuous delivery is an important skill and valuable technique in software development. This idea gathers a lot of focus at Red Gate as we build tooling to help with the challenges of implementing CD. However the idea of CD doesn’t mean that you constantly update your own software for customers. It’s entirely plausible to practice CD internally, releasing changes to test and staging environments many many times before you release a change to production. The idea in CD is that you know how to, and practice, deploying software regularly. That way you’re assured you can actually perform a release when you need to.

    Steve Jones

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 2.6MB) podcast or subscribe to the feed at iTunes and Mevio . feed

    The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.