How can we help you today? How can we help you today?

SQL Compare 14 Command Line on Linux

SQL Compare 14 has now been released and a new beta feature is that the command line interface can now be run on Linux, using a Docker container. The only thing you need to do to use it is to ensure Docker is installed on your Linux machine. The SQL Compare 14 container image is now live on Docker Hub.

As a basic example, you can use the following to compare two databases using the SQL Compare container image.

docker run --rm redgate/sqlcompare:14 /IAgreeToTheEULA \
    /s1:my-server\\sql2019 /db1:database1 /u1:sa /p1:my-password \
    /s2:my-server\\sql2019 /db1:database2 /u2:sa /p2:my-password
Here is a link to a page on our documentation site to help you get started.
Rob C
0

Comments

9 comments

Sort by
  • trurl
    This is awesome! 
    Gave is a try, having issue with stored proc referencing custom data type:
     Column, parameter, or variable #1: Cannot find data type
    This worked with sql compare 12 windows same setup. Where issues can be reported for sql compare docker 14?
    trurl
    1
  • Roseanna
    Hi everyone,

    To find out more about SQL Compare 14, check out this product learning article.

    Cheers,

    Roseanna
    Roseanna
    0
  • David_Keaveny
    This looks very helpful, especially for non-Windows based build systems. When I try to run the CLI based on the scripts, it fails to connect my local SQL Server - do we need to set up networking to allow the CLI access? There's no indication of it in the examples.

    My script is:
    <div>docker run --rm --interactive --tty \
 --mount type=bind,source=/src/scripts,target=/src \
  redgate/sqlcompare \
  /IAgreeToTheEULA \
  /Scripts1:/src \
  /Server2:localhost /Database2:MyDatabase /UserName2:Deployments /Password:my-secret-password
</div>
        which results in the error message:
    SQL Compare V14.7.2.20940
====================================================================================================================================================================
Copyright © Red Gate Software Ltd 1999-2022

Beta (expires on Wednesday, 06 July 2022)
Warning: Some settings are missing from the RedGateDatabaseInfo.xml file in the scripts folder '/src': default values will be used for any omitted setting.
Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify<br>that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server: Could not open a connection to SQL Server)
    David_Keaveny
    1
  • David_Keaveny
    Oops, never mind; I think the password was wrong!

    #FacePalm
    David_Keaveny
    0
  • talharizwaan
    This looks very helpful, especially for non-Windows based build systems. When I try to run the CLI based on the scripts, it fails to connect my local SQL Server - do we need to set up networking to allow the CLI access? There's no indication of it in the examples.

    My script is:
    <div>docker run --rm --interactive --tty \
 --mount type=bind,source=/src/scripts,target=/src \
  redgate/sqlcompare \
  /IAgreeToTheEULA \
  /Scripts1:/src \
  /Server2:localhost /Database2:MyDatabase /UserName2:Deployments /Password:my-secret-password
</div>
        which results in the error message:
    SQL Compare V14.7.2.20940
====================================================================================================================================================================
Copyright © Red Gate Software Ltd 1999-2022

Beta (expires on Wednesday, 06 July 2022)
Warning: Some settings are missing from the RedGateDatabaseInfo.xml file in the scripts folder '/src': default values will be used for any omitted setting.
Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify<br>that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server: Could not open a connection to SQL Server)
    wow, it looks rpomising,I am gonna give it a try and update you guys here . Thanks.
    talharizwaan
    0
  • abdullahsh5572
    It’s awesome that SQL Compare 14 now supports Linux via Docker! Just make sure Docker’s set up on your system, and then you can easily compare databases using the command provided. For more info, you can check out the Redgate documentation. Great feature for Linux users!
    abdullahsh5572
    0
  • goharclients
    @David_Keaveny
    Open SQL Server Configuration ManagerNavigate to SQL Server Network Configuration → Protocols for [Your Instance]Ensure TCP/IP is enabledRestart the SQL Server service after making changes
    goharclients
    0
  • MrNoland

    David_Keaveny said:

    This looks very helpful, especially for non-Windows based build systems. When I try to run the CLI based on the scripts, it fails to connect my local SQL Server - do we need to set up networking to allow the CLI access? There's no indication of it in the examples.

    My script is:
    <div>docker run --rm --interactive --tty \ --mount type=bind,source=/src/scripts,target=/src \  redgate/sqlcompare \  /IAgreeToTheEULA \  /Scripts1:/src \  /Server2:localhost /Database2:MyDatabase /UserName2:Deployments /Password:my-secret-password </div>

        which results in the error message:
     

    SQL Compare V14.7.2.20940 ==================================================================================================================================================================== Copyright © Red Gate Software Ltd 1999-2022 Beta (expires on Wednesday, 06 July 2022) Warning: Some settings are missing from the RedGateDatabaseInfo.xml file in the scripts folder '/src': default values will be used for any omitted setting. Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify<br>that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server: Could not open a connection to SQL Server)

    Sure! Your SQL Server connection issue likely happens because the Docker container sees `localhost` as itself, not the host machine. Try using `host.docker.internal` instead.
     

    MrNoland
    0
  • Lyant

    Still helpful in 2025, Thanks.

    Lyant
    0

Add comment

Please sign in to leave a comment.