Unable to execute Profiles.yml while creating dbt to SQL conection getting error as Database Error ('28000', "[28000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed for user 'None'. (18456) (SQLDriverConnect); [28000] [Microsoft][ODB

[nisha.sonawane]

Working Process Mining - Customizing data transformation - Seeting up Profiles.yml file and running the same.

However, getting following error -

Database Error
(‘28000’, “[28000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed for user ‘None’. (18456) (SQLDriverConnect); [28000] [Microsoft][ODBC Driver 17 for SQL Server]Invalid connection string attribute (0); [28000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed for user ‘None’. (18456); [28000] [Microsoft][ODBC Driver 17 for SQL Server]Invalid connection string attribute (0)”)
(venv) PS C:\My_transformations\TemplateOne-MultiFiles\models>

[Kosmas_Hatzidimitris]

Hi Nisha,

This error appears at least when the user setting is not filled in in the profiles.yml. Did you fill in the right login account?

Below settings are needed to connect to SQL server:

    sqlserver: 
      database: 
      driver: "ODBC Driver 17 for SQL Server"
      password: ""
      port: 
      schema: 
      server: 
      type: sqlserver
      user:

Extra info around profiles.yml can be found here too: Microsoft SQL Server setup | dbt Developer Hub

[nisha.sonawane]

Thank you so much @Kosmas_Hatzidimitris for your help, yep Script was almost same with values mentioned for given attributes, however one attribute was missing! which was mentioned in the document link that you have shared - Microsoft SQL Server setup | dbt Developer Hub (getdbt.com)

windows_login: TRUE

have added it to my profiles.yml with value set to true and it worked for me

Thanks a lot!

[nisha.sonawane]

This is how script looks like:

uipathTemplateOne:
outputs:
default:
type: sqlserver
driver: ‘ODBC Driver 17 for SQL Server’
server: servername
port: 1433
user:
password:
database: dbname
schema: schemaname
authentication: sql
windows_login: TRUE

target: default

Note: servername, dbname, schemaname has to be your own actual names of server, database and Schema respectively.