Difference between revisions of "Database connection string"
(Partial re-write to remove other, un-used, drivers) |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
==Example database connection string== | ==Example database connection string== | ||
| − | < | + | <pre> |
ConnectionType=MSSQL | ConnectionType=MSSQL | ||
| − | |||
| − | |||
| − | + | ConnectionString=ADO?AuxDriver=SQLOLEDB.1;Server=DBServer1;Database=BurnsInjury;UserID=burndbuser;Password=XXXXX | |
| + | </pre> | ||
| − | < | + | ''or'' |
| + | |||
| + | <pre> | ||
ConnectionType=MSSQL | ConnectionType=MSSQL | ||
| + | |||
ConnectionString=ADO?AuxDriver=SQLNCLI10.1;Server=DBServer1;Database=BurnsInjury;Integrated Security=SSPI | ConnectionString=ADO?AuxDriver=SQLNCLI10.1;Server=DBServer1;Database=BurnsInjury;Integrated Security=SSPI | ||
| − | </ | + | </pre> |
| Line 30: | Line 32: | ||
*ADO?AuxDriver=SQLOLEDB.1 - ''ADO DB Driver'' | *ADO?AuxDriver=SQLOLEDB.1 - ''ADO DB Driver'' | ||
*AnyDAC?AuxDriver=MSSQL - ''No external driver needed, AnyDAC is a fast, built in SQL Server driver that can be used at any time'' | *AnyDAC?AuxDriver=MSSQL - ''No external driver needed, AnyDAC is a fast, built in SQL Server driver that can be used at any time'' | ||
| + | |||
| + | '''Security & Logins''' | ||
| + | |||
| + | As shown in the two examples above, there are two methods of authenticating against the SQL Server; SQL Login or Windows Authentication. | ||
| + | |||
| + | To use an SQL Login provide the userid & password: | ||
| + | |||
| + | <pre>...;UserID=myuser;Password=mypassword</pre> | ||
| + | |||
| + | To use Windows Authentication, instead of the UserID & Password specify the following: | ||
| + | |||
| + | <pre>...;Integrated Security=SSPI</pre> | ||
| + | |||
| + | Note that using integrated security may require additional steps to allow the application server machine access to the database on a remote SQL server. | ||
| + | |||
| + | '''Restarting the Server'' | ||
If you change any settings in the AquilaServer.ini file, the AquilaServer service must be restarted for the changes to take effect. | If you change any settings in the AquilaServer.ini file, the AquilaServer service must be restarted for the changes to take effect. | ||
Latest revision as of 17:58, 13 June 2016
This is a Technical Instructions topic
The application server INI File contains two entries necessary to control the access to the database.
Example database connection string
ConnectionType=MSSQL ConnectionString=ADO?AuxDriver=SQLOLEDB.1;Server=DBServer1;Database=BurnsInjury;UserID=burndbuser;Password=XXXXX
or
ConnectionType=MSSQL ConnectionString=ADO?AuxDriver=SQLNCLI10.1;Server=DBServer1;Database=BurnsInjury;Integrated Security=SSPI
Alter the values in the string above to reflect your own installation as detailed below.
Driver and AuxDrivers
The driver and auxillary driver is the ADO?AuxDriver=SQLNCLI10.1' part of the connection string. In the above example it is ADO?AuxDriver=SQLNCLI10.1.1 which uses the SQL Native Client.
The following are your choices of drivers depending on what libraries you have available on the server:
- ADO?AuxDriverSQLNCLI10.1 - SQL Native Client
- ADO?AuxDriver=SQLOLEDB.1 - ADO DB Driver
- AnyDAC?AuxDriver=MSSQL - No external driver needed, AnyDAC is a fast, built in SQL Server driver that can be used at any time
Security & Logins
As shown in the two examples above, there are two methods of authenticating against the SQL Server; SQL Login or Windows Authentication.
To use an SQL Login provide the userid & password:
...;UserID=myuser;Password=mypassword
To use Windows Authentication, instead of the UserID & Password specify the following:
...;Integrated Security=SSPI
Note that using integrated security may require additional steps to allow the application server machine access to the database on a remote SQL server.
'Restarting the Server
If you change any settings in the AquilaServer.ini file, the AquilaServer service must be restarted for the changes to take effect.
