Voice of the DBA

Author: way0utwest

  • Developer Deployment Frustrations

    This editorial was originally published on Sept 7, 2012. It is being re-published as Steve is at DevConnections.

    Why don’t developers like SQL Server? Probably a few reasons, but I’m sure this is one that really frustrates them. I found a Connect Item that was titled:  Why is Deploying SQL Server 2008 R2 sooooo FRUSTRATING?!!  There really is a question there, asking for guidance on  which versions of SQL Server are available and recommended for developers to include in their applications.

    When SQL Server MSDE was released, it seemed that Microsoft was looking for it to be included in small applications that might then be upsized to a Standard or Enterprise edition of SQL Server. It seems to me that this is really the market for Express (the evolution of MSDE) and that it ought to be simple for a developer to not only deploy this with their application, but also setup basic maintenance easily.

    I sometimes think that the software developers at Microsoft get lost in their own specialty and forget just how frustrating it can be for the rest of us trying to use their product in new ways. They forget that many of us want to deploy simple solutions easily, and not spend a lot of time working out the nuances of software setup.

    I’d like to see Express not only have a very simple setup that works across multiple versions of Visual Studio, but also baic maintenance plans built in that allow full and log backups (if needed), along with index rebuilds with a simple switch set as a part of setup. A few registry keys or XML config changes could set paths or frequencies.

    Making life simpler for developers is a worthwhile investment for the SQL Server team. It makes them more likely to include it in their applications. If you can add a one-switch replication to sync to a Standard or Enterprise SQL Server, they might think Express is required in every application.

    Steve Jones

     

  • T-SQL Tuesday #83–The Same Old Issues

    tsqltuesdayThis month is an interesting T-SQL Tuesday topic, and it’s brought to us by Andy Mallon, with the topic of the same old issues we’re still dealing with. I think that’s an interesting issue, since I do find myself answering the same old questions over and over.

    If you’ve never participated, T-SQL Tuesday is a day when people should publish a post on the specified topic. This is a way to generate some posts and interest, and perhaps learning, about a topic. Share your thoughts, either on the second Tuesday of each month, or catch up later on your blog.

    We Still Don’t Restore

    I’d like to write something about T-SQL, and I could. Certainly SELECT * is an issue, or why we should not use old style joins (that’s almost gone), but there’s a SQL Server topic that I think bears repeating.

    A backup isn’t enough. You must also test restores.

    The reason isn’t complex, but plenty of people still don’t seem to understand why a backup isn’t enough. After all, if I copied a file, or I ran BACKUP DATABASE successfully, isn’t that enough?

    Suppose you had an issue at 3am and needed to restore a database on a new instance. You run this T-SQL:

    USE [master];
RESTORE DATABASE [Finances]
FROM DISK = N'D:\SQLServerBackup\MSSQL13.SQL2016\MSSQL\Backup\Finances.bak'
WITH FILE = 1,
    NOUNLOAD,
    STATS = 5;

GO

    And you get this error:

    Msg 33111, Level 16, State 3, Line 2
Cannot find server certificate with thumbprint '0xD9B9E685D465E29C11E15346D995DEF59E53B4A3'.
Msg 3013, Level 16, State 1, Line 2
RESTORE DATABASE is terminating abnormally.

    What do you do? Hopefully you recognize the issue and can fix the issue. Maybe more importantly, you have a backup of the missing certificate.

    Most people don’t deal with encryption, but you never know when your backup job might start failing, perhaps writing to a damaged file that appears to work (if you write as a device) but really isn’t capturing the backup file. Perhaps you don’t know that your backups are being written to a location and deleted a day later, but the process that is supposed to copy them to tape or a remote file share is broken.

    Any number of things can happen. The point is that you want to be sure that you are actually getting useable backup files.

    That means testing restores.

    It’s 2016. I shouldn’t have to remind anyone of this.

  • The Free-Con Returns to Seattle

    On Monday, October 24, 2016, there will be a Free-Con in Seattle for those that might not be attending a pre-con before the Pass Summit. Put on by Jason Brimhall and Wayne Sheffield, there’s a set of 6 sessions you can attend for free that day.

    Register now to come.

    They are asking for a $25 lunch fee to cover lunch, but you can opt out. However, please don’t register if you can’t come. I’m sure plenty of people want to go and extra registrations can upset planning.

    If you can come, the lineup is impressive:

    • Jason Brimhall
    • Wayne Sheffield
    • Grant Fritchey
    • Tjay Belt
    • Chad Crawford
    • Gail Shaw

    This is an alternative to other pre-conference sessions that PASS puts on, and you have to chance to learn about PowerBI, Temporal Tables, Wait Stats, Impact Analysis, and Azure SQL Data Warehouse.

    If you aren’t attending another event on Monday, perhaps you’d like to come to the Free-con and enjoy learning and discussing SQL Server with a few highly talented SQL Server pros.

  • Monday Night Networking at Summit 2016

    It’s PASS Summit time and that means Andy Warren and I are doing another Monday Night Networking Dinner.

    For those of you that haven’t come in the past, Andy and I aren’t buying you dinner. What we are doing is setting up a time and location for people to come and meet others that are attending the PASS Summit. This is a great chance to meet other data professionals if you don’t have any other plans.

    Details:

    Monday, October 24, 2016

    Location: The Yardhouse, 1501 4th Avenue, Seattle, WA (map)

    We are doing things a little differently to spread the load on the restaurant. It’s Monday night, which means football in the US. To try and ensure people can find a place to sit and meet, we’re asking you to sign up for tickets at a particular time and come down within 10-15 minutes of that time.

    The times are:

    5:30 – Sign up

    6:30 – Sign up

    7:30 – Sign up

    8:30 – Sign up

    Come down, join us, wear your Summit badge, and have a good time.

    You’ll have to buy your own food and drinks (or maybe some for a new friend), but it will be an enjoyable experience.