Command-line mode on macOS

Last modified: September 6, 2024

You can use Terminal to run dbForge Studio for SQL Server on a Mac.

Note

This topic describes the CLI-powered access to the functionality of dbForge Studio installed into a CrossOver bottle. For more information on the command-line functionality of the Studio, refer to the corresponding topics of the documentation.

As an example, let’s see how to compare schemas of two databases from Terminal. To do that, run the following command:

/Applications/CrossOver.app/Contents/SharedSupport/CrossOver/bin/wine --bottle 'dbForgeStudioSQL' --check --wait-children --start "C:\Program Files\Devart\dbForge Studio for SQL Server\dbforgesql.com" /schemacompare /source connection:"Data Source=[server_name/address];Integrated Security=False;User ID=[yourusername]; database=[database_name]" /target connection:"Data Source=[server_name/address];Integrated Security=False; User ID=[yourusername];database=[database_name]"

In this example:

/Applications/CrossOver.app/Contents/SharedSupport/CrossOver/bin/wine

…is the command that initiates CrossOver.

--bottle 'dbForgeStudioSQL'

…is the parameter that specifies the name of the bottle that contains dbForge Studio for SQL Server.

--check --wait-children --start

…are the options that configure the launch of the application.

"C:\Program Files\Devart\dbForge Studio for SQL Server\dbforgesql.com" /schemacompare /source connection:"Data Source=[server_name/address];Integrated Security=False;User ID=[yourusername]; database=[database_name]" /target connection:"Data Source=[server_name/address];Integrated Security=False; User ID=[yourusername];database=[database_name]"

…is the command to run the schema comparison with the specified options.

Worked example

Let us look at a worked example demonstrating how to compare two SQL Server databases.

/Applications/CrossOver.app/Contents/SharedSupport/CrossOver/bin/wine --bottle 'dbForge Studio for SQL Server'--check --wait-children --start "C:\Program Files\Devart\dbForge Studio for SQL Server\dbforgesql.com" /schemacompare /source connection:"Connection Timeout=20;Data Source=DBFSQLSRV\SQL2019;Initial Catalog=AdventureWorks2019;Integrated Security=False;Packet Size=1024;User ID=yourusername" /target connection:"Connection Timeout=20;Data Source=DBFSQLSRV\SQL2019;Initial Catalog=AdventureWorks2019Test;Integrated Security=False;Packet Size=1024;User ID=yourusername"

The schema comparison process begins.

Schema comparison from CLI

And finishes successfully.

Schema comparison from CLI

Run a batch file

You can run not only individual commands but also generated batch files (*.bat/*.cmd files), which are to be created as usual Windows batch files.

Let’s look at an example of code for a batch file.

/Applications/CrossOver.app/Contents/SharedSupport/CrossOver/bin/wine --bottle "dbForgeStudioSQL" --check --wait-children --start "C:\users\crossover\My Documents\compare.bat" 

In this example:

/Applications/CrossOver.app/Contents/SharedSupport/CrossOver/bin/wine

…is the command that initiates CrossOver.

--bottle 'dbForgeStudioSQL'

…is the parameter that specifies the name of the bottle that contains dbForge Studio for SQL Server.

--check --wait-children --start

…are the options that configure the launch of the application.

"C:\users\crossover\My Documents\compare.bat"

…is the parameter that specifies the path to the batch file.

Note

You can automate the launch of dbForge Studio from the command line using the standard macOS scheduler.