Category: Blog

  • AutoMap in SQL Compare

    SQL Compare is a core product from Redgate and I’ve got a series on some of the interesting things I’ve found. Download a trial today if you haven’t tried it.

    SQL Compare does a great job of trying to help you map columns in your database. For example, I was testing deployments recently to see how a process might work and I noticed the SQL Compare had automapped columns for me.

    This is a feature in SQL Compare that tries to make your development effort a little quicker and easier. As you can see in the image below, there’s a note at the top of the comparison, and then an indicator for the actual object.

    2017-12-01 12_37_01-SQL Compare - New project_

    If I click the object, I see the code, but I don’t know where the auto mapping has taken place.

    2017-12-01 12_37_09-SQL Compare - New project_

    In this case, I know because I changed the Quantity column name, but there’s nothing special here about the mapping. SQL Compare just mapped “Quantity” to “Qty” by itself. If I check the project properties, I can see the mapping, and change it if necessary.

    If you want to know how to customize this, I’ve got an article on the Redgate Hub on How to Customize Schema Comparisons using Auto Map in SQL Compare.

    Automap is one of those useful, handy features of SQL Compare. It gets you moving in development quickly by taking care of some work, but you can easily change things and keep your project handy if you have the need.

    .

  • T-SQL Tuesday #098–2018 Goals

    tsqltuesdayA great topic for T-SQL Tuesday this time from @sqlmal. It’s Setting Learning Goals for 2018, and it’s a topic I both loathe and love. I hate making commitments that I can’t keep, and I constantly find that a chaotic life will get in the way of learning over time.

    As an example, I tried reading the Powershell in a Month of Lunches book. I managed to get to Day 19. It’s not that I don’t like PoSh or have given up (I still blog on the topic). It’s that the setup was more complex later in the book (really need a domain) and I became busy at work.

    Goals do have a way of focusing a person on a task, and they’re good in that sense. With a year of less travel coming, this was a timely topic for me and forced me to stop and think a bit about the way I want to drive learning in 2018.

    Goals for 2018

    What do I want to learn next year? Here’s a short (ish) list, in no order:

    • CosmosDB
    • Python
    • Pester
    • Extended Events
    • Entity Framework

    I could try to tackle all of these, but that certainly won’t help me do well. This is too large a list to become strong at all of them, though I could spend time improving my skills a little bit in all these areas.

    Of these items, I could relate many of these to my job, which can make it hard to choose. In addition to these items, I’ve got other things that I know will be a part of my learning next year. Product changes, new integrations between our products and others, plus who knows what will come about.

    Picking Two

    If I have to say that I’ll spend 100 hours on something next year and try to get better, I’ll say that the two areas I’ll focus on are Extended Events and Python. While I may dabble in the others, I think that these two areas will be more important to my career as well as my job over time.

    I need a much better understanding of how XE works apart from trace, and I need a lot more comfort in gathering and analyzing the data.

    I also think that Python, with its addition to SQL Server ML and the popularity of the language in new packages and modules means that this is an area that provides some variety, excitement, and a relation to my job. Plus, it’s in SQL Data Generator, so I should have lots more examples there.

    My goals for these two are to spend 50 hours on each over the year, in a combination of course work (articles, videos, etc.) and practical work (building things and trying to use the technology to solve problems).

    Caveats

    There’s always something that comes up, and while I don’t want to start making excuses, I recognize that there are a few things that might derail my plan and make me change.

    First, GDPR. I have no idea how this will impact Redgate and my, but I might need to spend a bunch of time early in the year on this. We are getting calls, questions, and requests from clients, and as some of our new integrations and products come out, this might eat up time.

    Second, travel. I haven’t planned on much, but I’ve really only set the first 4 months of the year. After that, we’ll see. Who knows what might come up or what demands arise.

    Third, life at home. I never know what will happen here and how things might change, so that could change how I focus. Plus, I have a sabbatical coming, so we’ll see how that affects me.

    Getting Ready

    I’m doing a few things right now. First, I’m setting a monthly reminder to update my goal progress. I’ll try to write a post each month, for better or worse, on where I am.

    2017-12-06 17_22_15-Appointment Recurrence

    Second, I’m setting an appointment for myself to sit down and plan some things out the last week of December. That’s a good time to spend an hour or two and try to come up with a plan. It won’t be perfect, but it will give me a direction on which to start. I can amend this during my monthly review if needed.

    That’s it, thanks to Mala for a great topic, and we’ll see how it goes.

  • Renaming a Column–#SQLNewBlogger

    Another post for me that is simple and hopefully serves as an example for people trying to get blogging as #SQLNewBloggers.

    One of the things I rarely do is rename objects. There are good reasons to do so, but often the changes required in other objects and applications isn’t worth the hassle. This is one reason why it would be good to spend a few minutes in design and come up with good names from the beginning.

    In any case, do you know how to do this? You could use SSMS and easily change the design of the table. Of course, SSMS might try to rebuild the table, which might not be what you want. Hopefully that’s not the case, though you should always get the script instead of just saving the change.

    The code you’d like to see is a simple meta data change that uses sp_rename. In my case, I want to change Qty to Quantity. I’d use this code:

    EXEC sp_rename @objname = ‘Sales.OrderLines.Qty’ ,
    @newname = ‘Quantity’ ,
    @objtype = ‘column’;

    I wish we had a direct ALTER TABLE statement that worked here, or better yet, an ALTER TABLE that allowed the entire table code to be shown (that’s not coming), but I’m not holding onto any hope that Microsoft will change this.

    If you’re a person that thinks you might need a temp table that you insert data into and then two renames of the tables, that’s not the best way. Simple meta data changes are always preferred.

    SQLNewBlogger

    I ran into this while helping someone test a change and thought this was a good, easy reminder of how to change names. You could show you understand this in a blog in five minutes.

  • SSMS Updates in 17.4

    SSMS 17.4 is out, and if you haven’t upgraded from SQL 204, 2012, 2008, etc., you should do so. You can run your bundled SSMS side by side with the new versions, but it seems that the 17x versions are improving andbecoming more stable.

    You can download the new version and use it for free. That alone should be a reason to update your workstations.

    This update includes a few new interesting items.

    • Vulnerability Assessment – Scanning for security and misconfiguration issues
    • Always On Dashboard – New latency reports
    • Showplan – some fixes and new operator icons
    • XE Profiler – Very cool to see this being enhanced.

    There are other updates and fixes as well. I’m sure there are some bugs, but for the most part, I think that SSMS 17.x is the way to go forward.