Database Connection Options
Campaign Enterprise is designed to work directly with any ODBC (Open Database Connectivity)
compliant database. Examples of ODBC databases include SQL Server, MySQL, Oracle, DB2, and most other true relational databases. Campaign also
connects directly to MS Access database .mdb or .accdb files. ACT is not a true database, is not ODBC compliant and does not
directly interface with Campaign Enterprise.
In order for Campaign to communicate with a database, you must set up a database
connection on the computer on which Campaign is installed. There are two types of connections you can use:
ODBC
An ODBC connection is set up in your operating systems control panel.
To create a new ODBC connection, find your control panel either through the start menu or using the search feature.
- Control Panel
- Administrative Tools
- Data Sources (ODBC)
Once inside the ODBC area, click on the system DSN tab and add a new DSN (Data Source Name) using the connection driver for your flavor
of database. Once the system DSN is named and created, it will be available in the Datasource page of the Campaign Edit screens when you
click Browse. Select the name, enter any authentication necessary into the string and tab out of the field to populate the table fields.
64 Bit vs. 32 Bit Systems
A problem arises if your Campaign is built on a 64 bit operating system. The Data Sources section in the Administrative tools of the control
panel uses 64 bit drivers, which do not show up in the Datasource edit screen. Campaign will only use 32 bit drivers. There are two options
to avoid this problem, build 32 bit drivers, or use an OLE DB connection string.
Adding a 32 Bit DSN
Microsoft has hidden the 32 bit Data Sources (ODBC) tool to make it more difficult to find, even though there are plenty of uses for
32 bit drivers. Some of the locations may include:
- C:\Windows\sysWOW64\ODBCad32.exe
- C:\Windows\system32\ODBCad32.exe
- C:\Windows\system32\en-US\ODBCad32.exe
If you are unable to find it in those directories, do a search for the ODBCad32.exe file.
Using an OLE DB Connection String
There is no clear definition as to what OLE DB stands for, but it is an alternative database connection option to using an ODBC connection. OLE DB
strings are typically more functional, less restrictive, faster, and more configurable. These connections can use native clients
already included in the operating system or clients you download and add. The primary resource for these types of connections is
Connectionstrings.com. Some of the strings you will find on that page include:
- SQL Server 2008, Standard Security: Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
- MySQL Named Pipes: Server=myServerAddress;Port=-1;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
- Oracle Dedicated Server Instance: Data Source=username/password@myserver/myservice:dedicated/instancename;
Other strings are available for these databases:
- Sybase
- IBM DB2
- Informix
- Postgres SQL
- AS/400
When connecting applications, there are several layers through which the connection
must traverse. Using OLE DB, you can bypass two of these layers, which improves performance. Many OLE DB strings are less restrictive
of what datatypes can be passed back and forth to Campaign. For example, ODBC does not transfer information from CLOB type fields,
but OLE DB does allow interactions.
MS Access
If you are using a MS Access database, you can simply browse to the file in the directory. The database must be on the same drive
on which Campaign is installed in order to work properly. If your table uses linked tables, those are not available for the write
back features used by Campaign.
Regardless of the type of database you use, there is a way to connect it to Campaign
to take full advantage of all the write back features available. Make sure that the connection method you use allows for updating the
database.
Return
to Articles |
