Difference between revisions of "Database connection string"

From EHS Help
Jump to: navigation, search
m
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{ProductTopic|Technical|Instructions}}
 
{{ProductTopic|Technical|Instructions}}
  
 
{{todo|Add connection options}}
 
  
 
The application server INI File contains two entries necessary to control the access to the database.
 
The application server INI File contains two entries necessary to control the access to the database.
Line 8: Line 6:
 
==Example database connection string==
 
==Example database connection string==
  
<code>
+
<pre>
 
ConnectionType=MSSQL
 
ConnectionType=MSSQL
 +
 
ConnectionString=ADO?AuxDriver=SQLOLEDB.1;Server=DBServer1;Database=BurnsInjury;UserID=burndbuser;Password=XXXXX
 
ConnectionString=ADO?AuxDriver=SQLOLEDB.1;Server=DBServer1;Database=BurnsInjury;UserID=burndbuser;Password=XXXXX
</code>
+
</pre>
 +
 
 +
''or''
 +
 
 +
<pre>
 +
ConnectionType=MSSQL
 +
 
 +
ConnectionString=ADO?AuxDriver=SQLNCLI10.1;Server=DBServer1;Database=BurnsInjury;Integrated Security=SSPI
 +
</pre>
 +
 
  
 
Alter the values in the string above to reflect your own installation as detailed below.
 
Alter the values in the string above to reflect your own installation as detailed below.
  
==Driver and AuxDrivers==
+
'''Driver and AuxDrivers'''
  
The driver and auxillary driver are the first two options specified in the connection string. In the above example it is ''ADO?AuxDriver=SQLOLEDB.1'' which uses the SQL OLE DB driver that is part of ADO.
+
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.
  
[[AquilaCRS]] has it's own, built in database drivers available.  We call this technology '''AnyDAC''' as it can connect natively to a host of database engines.  Our own MSSQL drivers are usually faster than using ADO.
+
The following are your choices of drivers depending on what libraries you have available on the server:
  
===MSSQL===
+
*ADO?AuxDriverSQLNCLI10.1 - ''SQL Native Client''
*ADO?AuxDriver=SQLOLEDB.1
+
*ADO?AuxDriver=SQLOLEDB.1 - ''ADO DB Driver''
*AnyDAC?AuxDriver=MSSQL
+
*AnyDAC?AuxDriver=MSSQL - ''No external driver needed, AnyDAC is a fast, built in SQL Server driver that can be used at any time''
  
===MySQL===
+
'''Security & Logins'''
*AnyDAC?AuxDriver=MYSQL
+
  
===Interbase===
+
As shown in the two examples above, there are two methods of authenticating against the SQL Server; SQL Login or Windows Authentication.
*IBX;
+
*AnyDAC?AuxDriver=IB
+
  
===Firebird===
+
To use an SQL Login provide the userid & password:
*AnyDAC?AuxDriver=IB
+
  
==Server, Database and User==
+
<pre>...;UserID=myuser;Password=mypassword</pre>
  
Replace the values in the above connection string with your own Server, Database, UserID and Password parameters.
+
To use Windows Authentication, instead of the UserID & Password specify the following:
  
==Connection options==
+
<pre>...;Integrated Security=SSPI</pre>
  
===MSSSQL===
+
Note that using integrated security may require additional steps to allow the application server machine access to the database on a remote SQL server.
  
===MySQL===
+
'''Restarting the Server''
  
===Interbase===
+
If you change any settings in the AquilaServer.ini file, the AquilaServer service must be restarted for the changes to take effect.
  
===Firebird===
 
  
===SQLite (local)===
 
  
 
[[Category:Admin Help]]
 
[[Category:Admin Help]]
 
[[Category:AquilaCRS]]
 
[[Category:AquilaCRS]]
 
[[Category:IBID]]
 
[[Category:IBID]]

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.