#1
Posted 03 September 2020 - 05:28 PM
This is your captain speaking. We may experience some slight turbulance and then...explode.
#5
Posted 07 September 2020 - 06:07 PM
you can set the dbname for sqldefault in the connection string in the format sqlusername/sqlpassword/dbname
Hi Wim,
Thanks. At the moment, our SQL Server connection string in the Dashboard is
Username/Password@<server>/<installation name>
Would we put the DBName before the @?
This is your captain speaking. We may experience some slight turbulance and then...explode.
#6
Posted 07 September 2020 - 06:10 PM
Check your Default Virtual Machine Profile. There are also settings there for your default DB
Has caught me out a few times
Hi Neil,
Thanks. Could you put up a screenshot showing that, or email it to Marlon.seton@swallowtech.com if its not possible to put a screenshot on here, please?
This is your captain speaking. We may experience some slight turbulance and then...explode.
#7
Posted 08 September 2020 - 07:04 AM
you can set the dbname for sqldefault in the connection string in the format sqlusername/sqlpassword/dbname
Hi Wim,
Thanks. At the moment, our SQL Server connection string in the Dashboard is
Username/Password@<server>/<installation name>
Would we put the DBName before the @?
Hi Marlon,
Perhaps we mean the same as long as dbname or installation name matches the name in the odbc driver. On my configuration @server is not used, and the database connection is ok
Wim
#8
Posted 17 September 2020 - 02:37 PM
you can set the dbname for sqldefault in the connection string in the format sqlusername/sqlpassword/dbname
Hi Wim,
Thanks. At the moment, our SQL Server connection string in the Dashboard is
Username/Password@<server>/<installation name>
Would we put the DBName before the @?
Hi Marlon,
Perhaps we mean the same as long as dbname or installation name matches the name in the odbc driver. On my configuration @server is not used, and the database connection is ok
Wim
Hello Wim,
Thanks for your help. Having "sqlusername/sqlpassword/dbname" in the connection string worked.
We have a separate environment variable where we put "sqlusername/sqlpassword@server/registration" which we parse for loading data into tables, hence my somewhat confusing post about having this in SQL_DBNAME.
This is your captain speaking. We may experience some slight turbulance and then...explode.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users