What I found out, quite by accident, is that if I went into the GUI and created my connections and then referenced them in the server argument of the /connection switch, it worked just dandy. I'm finalizing evaluation phase and spent waaaay too much time trying to figure this out when it could have been so simple.
Here is an example of my PowerShell command:
Code: Select all
PS C:\Program Files\Devart\dbForge Schema Compare for SQL Server> .\schemacompare /snapshot /compress:True /connection:server=DW /database:SomeDB /file:"i:\Snapshots\SomeDB_Snapshot.snap"
I tried adding the Integrated Security=True and received a /connection invalid error.Error: Login failed for user ''.
I tried adding my User ID (even though we don't use SQL Server Logins) and received a /connection invalid error.
I tried using the full connection string I've used successfully for setting /source and /target connections and I get a /connection error.
Can dbForge support beef up the documentation with regards to connection strings, particularly what is required if you don't want to use the GUI at all?