Closed BlackbirdSQL closed 8 months ago
This is because the SE considers your new connection an equivalent connection. More on equivalency can be found here.
As of BlackbirdSql build 10.0.2.0 equivalency keys are configurable under the BlackbirdSql Server Tools
DDEX options.
So the simplest way to create a new "non-equivalent" equivalent connection would be to set the Application Name
connection property as an equivalency key, then give each distinct equivalent connection it's own unique Application Name
, eg. "Connection for App1", "Connection for App2".
As of release 10.1.0.0, Application Name
now defaults to an enabled optional equivalency key.
Using Application Name
as a means of distinguishing unique "non-equivalent" equivalent connections is recommended over any other connection property because BlackbirdSql recognizes it as a Weak Equivalency Key
, This means that it will not have to build separate Trigger/Generator linkage tables for it if other connections already exist where they are only differentiated by Application Name
.
In some instances creating a new Server Explorer connection will do nothing and revert to selecting an existing connection in the SE.