6 October 2017
6 October 2017

Remembering passwords in SQL Compare and SQL Data Compare

We’ve recently added a feature to automatically populate your SQL Server credentials when you’re using SQL Compare or SQL Data Compare. If you check the Remember credentials box, passwords will now be stored in two places: the Windows Credential Store and your project file if you save one.

The project file has long been a way to share comparisons and you can still save your credentials there. However, this doesn’t do the whole job if you often make the same comparison between many different environments, tediously entering the password for each server when you edit the project.

Enter the Windows Credential Store: if you choose to save your password, it will now be stored here even if you don’t save a project. This means it can be filled in automatically next time you connect to the same server from SQL Compare or SQL Data Compare.

The Credential Manager in the Windows Control Panel has a tab called Windows Credentials where you can manage credentials saved by many applications. The ones saved by SQL Compare and Data Compare have names like Redgate SQL Connection [MyServer] and you can delete any you don’t want from there. (Side note: the stored value is actually a connection string to support different authentication methods. If your password changes, it’s easiest to re-enter it in the Edit Project dialog).

SQL Comapre password 2

If you don’t want any new passwords to be stored, just ensure the Save password box in the Edit Project dialog is unchecked. This will disable both types of password storage, so passwords will not appear in the Credential Store and your project files will be safe to distribute.

It’s the sort of feature you might have used without even noticing. SSMS and SQL Doc have remembered passwords for a long time now, and it was a popular suggestion on the SQL Compare UserVoice page. If there are other features you’d like to see in SQL Compare or SQL Data Compare, please let us know.

Tools in this post

SQL Compare

Compare SQL Server schemas and deploy differences fast.

Find out more

SQL Data Compare

Compare and deploy SQL Server database contents.

Find out more

Share this post.

Share on FacebookShare on Google+Share on LinkedInTweet about this on Twitter

Related posts

Also in Hub

Finding code smells using SQL Prompt: procedures that lack schema-qualification

SQL Prompt implements a static code analysis rule, PE001, which will check code automatically, during development and testing work, for occurrences of a stored procedure being called, via the EXECUTE ...

Also in Product learning

How SQL Monitor Monitors Azure-based SQL Server Failover Cluster Instances

If you're working with SQL Server, one of the most appealing features of cloud-based computing services, such as Azure and AWS, is that they make it so much easier to design systems that are both high...

Also in SQL Compare

Keeping track of history: SQL Compare and Temporal Tables

SQL Compare 13 introduces support for deploying changes to temporal tables, which were introduced in SQL Server 2016. This means that any changes made to the definition of a temporal table in a source...

Also about SQL Compare

How to Customize Schema Comparisons using Auto Map in SQL Compare

It's a tedious task to have to compare two versions of a SQL script, side by side, for example to find differences between the version of the script on Production, and the one on the Test system. As a...

Also about SQL Data Compare

How to deploy a database plus static data using SQL Compare and SQL Data Compare

We can use the SQL Compare Pro command line with PowerShell to automate the process of creating a new build script for a version of the database, from the object scripts in the VCS. However, what if w...