Voice of the DBA

Tag: sql server

  • The Default DBA

    When we setup SQL Server, there are a few choices we need to make, some of which require a few items be prepared in advance. Service accounts are one of those preparation tasks that DBAs usually perform in advance of installing an instance. There are a few things, however, that aren’t configured when SQL Server is installed, like alerts and operators. I find that often these items can be missed by inexperienced DBAs, who forget to configure standard alerts. They might also not have a mail account ready, which is required for the instance to send mail.

    Perhaps there’s a better way for SQL Server to request this information when it is installed. If one part of the setup program asked for default mail information, it would be easy to pre-configure the instance to setup alerts and enable them for communication with a DBA. Personally I’d prefer that setup get a mail profile and a default DBA group email address that receives information about the operation of the instance that the DBA should be aware of.

    There can be a hesitation from experienced DBAs that don’t want setup to install mail for them, but it would be easy to make this an optional component, with a checkbox like the one for a blank sa password. You actively choose to install the server differently if necessary, but otherwise setup would push DBAs to ensure that notifications are configured. We could even see a pre-selected list of alerts that will be enabled, with the option to disable all or just selected items.

    I don’t know that Microsoft will build these types of defaults into SQL Server, but I wish they would. We’ve done that with SQL Monitor at Red Gate, and we have seen the advantages that come when you provide good practices and knowledge to less experienced DBAs: they gain some knowledge transfer and have software running at a high level from the very beginning.

    Steve Jones

    The Voice of the DBA Podcasts

    We publish three versions of the podcast each day for you to enjoy.

  • Speaking at Oracle Training Days

    RMOUGSpeakerA first for me. I’m attending a non-SQL Server event, trying to bring a little knowledge of my platform to those that typically work on the Oracle side of things.

    The Rocky Mountain Oracle Users Group is holding their Training Days 2013 event on Feb 11-13 in Denver and a few of us SQL Server people were invited to speak.

    I’ll be talking about Database Maintenance one of the days, hopefully ensuring that some of the “accidental” SQL Server DBAs that also manage Oracle understand the basics of maintenance in SQL Server.

  • Feedback is Encouraged

    Most of us have complaints and criticisms of the software we use, including SQL Server. We see the failings of the software, the places where it forces us to work harder than we’d expect to work to accomplish a task. That’s expected, since the design of any piece of software, from Notepad to SQL Server, involves design decisions that are geared to solve some problems, not all problems.

    As a side note, this is one of the places where third party tools can improve the operation of software that allows plug ins. Small companies often build utilities that solve specific problems, and if you are irritated by something in SQL Server, consider looking at third party tools. My employer, Red Gate software makes software designed to make the DBA or developers’ job easier, but there are some great tools out there from execution plan explorers to reporting add ins for SQL Server.

    However Microsoft does try to improve SQL Server regularly. This week I saw Chris Webb note that the SSAS team is looking for feedback. In the past we’ve run various surveys at SQLServerCentral for Microsot and as an MVP, I’ve noted that more and more of the specialized groups working ont he SQL Server platform are sending out surveys about their particular features. I’ve seen Microsoft ask for feedback on how the platform is working for you.

    Change doesn’t always occur as fast as we’d like, and there have been no shortage of issues with the Connect system, but I have seen it work well in a number of cases. I do think Microsoft is listening, and I appreciate that. However I also realize that my feedback is just an opinion, not a vote in what gets implemented in the next version of SQL Server.

    I encourage you to give feedback when you get the chance. Your particular suggestion or bug might not seem important, but if enough customers submit the same feedback, I’m sure it will get implemented in the platform.

  • SQL Server Thumbnail Metrics – OS Memory

    I’m gathering a few metrics around the Internet for SQL Server from people that I think really know how to run a SQL Server. This is a series of posts that I’m making to gather these metrics up for easy access later.

    Host Memory

    The short metric is:

    Leave 4GB for the OS, or 10% of physical (or guest) memory, whichever is greater.

    Examples: If I have the following amounts of RAM, I leave this for the OS.

    • 16GB of RAM – leave 4GB since 4 > (16 * 10%)
    • 32GB – leave 4GB since 4 > (32 * 10%)
    • 64GB – leave 6.4GB since (64 * 10%) > 4

    Essentially leave 4GB until you get to 48GB of RAM, then go to 10%.

    References: Mr. Brent Ozar of Brent Ozar, PLF who’s presented and written this a few times, but the reference I’m using is: How to Set SQL Server Max Memory for VMware

    Explanation: In the older x86 days there were all sorts of rules for setting memory for the OS and SQL Server. I won’t go into those, and for the time being we’re working in the x64 world, not x128. For that, you need to be sure the OS isn’t starved by SQL Server and unable to manage the host processes. These days 32GB isn’t expensive, and 4GB gives you a nice cushion at lower levels. At higher ones, you need