You can connect SQL Server databases in Exportizer using these ways:
1. Opening through FD interface. Select FD interface, click SQL Server, then fill all needed database parameters.
Example of configuring a database connection:
(required parameters are highlighted)
| Vendor library | |
| Server | localhost\SQLEXPRESS |
| Database | master |
| OS authentication | Yes |
| Application name | Database Tour Pro |
| User name | |
| Password | |
| SQL command separator | <mssqlgo> |
2. Opening through ODBC DSN. Create (if it does not exist yet) an ODBC DSN of the corresponding type using Windows ODBC Data Source Administrator, and point it to your database. Then select ADO or BDE interface, choose ODBC data source option and then select the needed ODBC DSN from the drop-down list.
3. Opening through connection string (interface: ADO). Select Connection string option and write a connection string. This way is the most flexible one because it allows to specify many additional parameters in the connection string and override standard Exportizer connection behavior. But it is recommended basically for advanced users. Here are basic connection strings (more examples and details can be found in the Internet):
Provider=sqloledb;Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword; (Microsoft OLE DB Provider for SQL Server must be installed)
Driver={SQL Server};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword; (Microsoft SQL Server ODBC Driver must be installed)
Provider=SQLNCLI;Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword; (SQL Native Client 9.0 OLE DB provider must be installed; use it for SQL Server 2005, see note below)
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword; (SQL Native Client 9.0 ODBC Driver must be installed; use it for SQL Server 2005, see note below)
Provider=SQLNCLI10;Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword; (SQL Server Native Client 10.0 OLE DB Provider must be installed; use it for SQL Server 2008)
Driver={SQL Server Native Client 10.0};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword; (SQL Server Native Client 10.0 ODBC Driver must be installed; use it for SQL Server 2008)
Provider=SQLNCLI11;Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword; (SQL Server Native Client 11.0 OLE DB Provider must be installed; use it for SQL Server 2012+)
Driver={SQL Server Native Client 11.0};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword; (SQL Server Native Client 11.0 ODBC Driver must be installed; use it for SQL Server 2012+)
Provider=SQLNCLI11.1;Integrated Security=SSPI;Persist Security Info=False;User ID="";Initial Catalog="";Data Source=localhost\SQLEXPRESS; (SQL Server Native Client 11.1 OLE DB Provider must be installed; use it for SQL Server 2012+)
Attention
- This database type is supported only in Exportizer Enterprise and Exportizer Pro (the latter one can open such databases via ODBC only).
- It is recommended to use SQL Server Native Client only for SQL Server 2005+ databases and when you need to use SQL Server 2005+ features.
- SQL Server client must be installed. The bit-version of it (32 or 64) must match the bit-version of the application.
- When choosing the ODBC option, please make sure the corresponding ODBC driver installed and the bit-version of it matches the bit-version of the application (32 or 64).
Notes
- Each Exportizer edition has both 32-bit and 64-bit versions. You can install both and use them depending on what type of database you need to work with.
- You can invoke the ODBC Data Source Administrator directly from Exportizer when it was launched in administrator mode:
See also