Tag: SQL Compare

A client asked for a summary of changes, so I wrote a post to show where to find this in SQL Compare 15. As I was checking out the Summary, I realized there are different ways to present this info, which can make your job as a data professional easier. This post shows the different views.

In the previous post, I showed this image, which is the default view. This lists the changes by object, meaning that I see the objects listed on the left with schema and name, and then the actions on the right. In the image below, the first item on the left is dbo.Street, with two items after it. On the right, we see this is a need to drop a PK and then create a new PK.

This is a good list, but there are other choices. In the upper right, there is a drop down. If I click it, I see this:

The Object is the default one, but if I click Modification, I see this view, which lists the types of changes. You can see that I have 1 drop PK, 4 table alters, 1 view alter, etc.

A good view, though I don’t often case about this, other than I usually would look for drops because those are problematic.

The third view is the modifications, but in the order they’ll take place. I like this, since as someone who has been a production DBA, I want to know what changes are happening in what order.

In this view above, the alters are split out. So I get one alter of a table, BaseTable, then a view, then a refresh, then alters for two other tables.

Using these summary views are good ways to initially conduct a review of what is changing for a deployment. This is valuable because for a lot of changes, this makes sense. For some, I might want to see the code, so having the changes in order here let me quickly find this change in the script and view the exact way this is going to be deployed.

SQL Compare is an amazing tool and it makes life much easier. If you haven’t tried it, download an eval today and give it a try. If you’d like to see this in a pipeline or more automated system, give the Flyway suite of tools a try.

A client asked for a summary of changes, so I wrote this quick post to show where to find this in SQL Compare 15.

If you use SQL Compare, you might find yourself in situations like this, where there are a bunch of changes.

This isn’t a lot, but when you build the script, you then are confronted with a lot of information. If I choose all those objects, here’s my script in the deploy wizard.

This is a lot of code to look through. Most people can do this, but it’s also easy to miss something in this long listing. Humans make mistakes, and we want to minimize mistakes.

The UX isn’t great, but if you look at the top of the code window, below the 14 objects part, there are three items: Deployment Script, Summary, and Warnings. If there are significant warnings, that will actually be the default screen, but the summary is something people miss. You can see this below:

If I click Summary, I see this:

This is a much more manageable list of things that are being touched, and a good list to show in a standup or code review for others to watch.

Grabbing a screen shot is something you could easily send to people as well. If you use the Flyway solution, we’ll also generate a report of this with your CI or deployment processes.

Give this a try the next time you use SQL Compare. If you don’t use it, give it a try. It’s amazing.

Actually, this is a change for many products and software that connects to SQL Server. Updated drivers require us to now decide to trust the server certificate.

I opened a project recently in SQL Compare 15 to check something for a friend. I went to run the compare and saw this:

At first I thought that one or both of my instances were broken, but I realized that this is a security issue. Updated drivers changed the default encryption options, which means we need to specify this.

The products at Redgate have been getting updated across the last year to add in a “trust server certificate” box. It’s not set by default, which I find annoying, as I rarely find SQL Server’s with certs. Certainly none of my test instances, and I wish I could set this to check by default.

In any case. when I check the boxes in the image above, the compare runs.

Something to keep in mind and a muscle habit to build if you still use SQL Compare often. If you don’t, give it a try. It’s amazing.