When calling dbt debug from windows using the following profile, the windows login defaults to the Fabric adapter implementation, which omits the port from the connection string.
DRIVER={ODBC Driver 18 for SQL Server};SERVER=0.0.0.0;Database=data_base;trusted_connection=Yes;encrypt=No;TrustServerCertificate=Yes;APP=dbt-sqlserver/1.7.4;ConnectRetryCount=1
When using a the standard sql login flow, it adds the port as expected.
Solved by either adding the port to the SERVER line (0.0.0.0,1444) + communicating this to users or lifting the windows login piece out of fabric into this adapter.
When calling
dbt debug
from windows using the following profile, the windows login defaults to the Fabric adapter implementation, which omits the port from the connection string.this resolves to
DRIVER={ODBC Driver 18 for SQL Server};SERVER=0.0.0.0;Database=data_base;trusted_connection=Yes;encrypt=No;TrustServerCertificate=Yes;APP=dbt-sqlserver/1.7.4;ConnectRetryCount=1
When using a the standard sql login flow, it adds the port as expected.
Solved by either adding the port to the
SERVER
line (0.0.0.0,1444
) + communicating this to users or lifting the windows login piece out of fabric into this adapter.