Campaign Enterprise can connect to any ODBC compliant database, one that complies with Open Database Connectivity requirements. These include, but may not be limited to the following:
Set up database connection:
You can now create a new external email list, using this connection string. All available connection strings will show in the drop down and you would select the one you need for a particular list.
By: Chris Lewis
The choice of the SMTP server you use is as if not more important that the email marketing tool you us. You can create the best looking, most effective email ever but if your SMTP server setup is not set up well then it is like you never sent it.
SMTP servers are the email work-horses of the internet. In the world of amazing technology, it is sometimes hard to be impressed, but I am constantly amazed by the thought and foreknowledge of the whole SMTP server framework. As time has moved on, the SMTP framework has changed, and the biggest change is that of SPAM control. There are to main problem areas we see daily with SMTP servers: How to connect to your SMTP server, and how "good" your SMTP actually functions.
SMTP Connection - The problems that are encountered when connecting to SMTP servers are varied and usually include these:
SMTP Providers - There are specialized companies out there that will act as your SMTP server. They will ensure your emails going out are appropriately make to conform to SPAM rules, they monitor their servers to make sure they are not blocked, and they will help you resolve issues that do come up is there are any problems with email recipients. Now it is true this will cost you some money, but if you add up all the time you or someone you will hire to work on these issues I think the value is there. If you are sending 100,000 emails a month, then the prices are really reasonable. If you send over a million, then that is maybe when you can start thinking of having your own SMTP server, but it really depends on the connectivity, your budget, and your expertise. One of our partners is SMTP.com (http://arialsoftware.smtp.com) and they have been a great partner with us for years. There are others, but I think they are the best, so check them out if this seems like a solution for you.
Many email professionals use Microsoft's Exchange server to send out their emails from Campaign Enterprise or Email Marketing director. The number one complaint we get is usually that it is very slow even though they are on "a super fast system on a fast internet connection." By default, Exchange Server is not setup to be a mass email system. In fact, they have created many settings by default to stop email from being accepted at a rapid pace. Depending on your Exchange Server version, there are settings you can look at to stop this throttling. A prominent term used is "tarpitting." Now the subject of tarpitting mainly concerns a set of parameters you can set in your Exchange Server so that it will accept emails at a rapid pace. Because of all the version of Exchange Server out there, and with them trying to deal with the SPAM issue through time, there are different settings for each of these versions which we cannot cover, but hopefully this article will uncover a nagging problem you might be having. Now keep in mind, many Exchange Server administrators may not even know what you are talking about because it is a rare occurrence and they probably have not encounter it before, so you may have to prime the pump with some Google service on "Exchange Server SMTP slowness" and show them some of the settings they will have to deal with.
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:
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.
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:
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:
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.
If your OLEDB driver is not loaded on the CE computer, you have to download it and install it (making sure you get the correct 32 or 64 bit version) download it here
Then scroll down to "Microsoft SQL Server 2008 Native Client"
if CE is on a 32 bit machine, then download the x86 package
and install it.