EMS logo

Products Navigation

Data Export for SQL Server

Our Partnership Status

Microsoft Certified Partner
Oracle Certified Partner
Embarcadero Technology Partner

EMS Data Export for SQL Server

On-line Documentation

EMS Data Export FAQ


Please read this page attentively if you have questions about Data Export for SQL Server.

 

 

Table of contents

 

 

 

 

Question/answer list

 

Q: What is EMS Data Export for SQL Server?

A: EMS Data Export for SQL Server is a powerful program to export your data quickly from SQL Server databases to any of 20 available formats, including MS Access, MS Excel, MS Word (RTF), HTML, XML, PDF, TXT, CSV, DBF and others. Data Export for SQL Server includes a wizard which allows you to set export options for each table visually (destination file name, exported fields, data formats, and much more) and a command-line utility to export data from tables and queries in one-touch.

 

 

Q: What do I need to start working with EMS Data Export for SQL Server?

A: First of all, you must have a possibility to connect to some local or remote SQL Server to work with Data Export. You can download SQL Server from http://www.microsoft.com/downloads/. Besides, you need your workstation to satisfy the system requirements for Data Export for SQL Server.

 

 

Q: What is the difference between the Export feature of SQL Manager for SQL Server and the Data Export for SQL Server standalone utility?

A: First of all, Data Export for SQL Server works faster as it is a considerably lighter application. Besides, it provides additional features for query building, namely:

  • export data from/to several tables simultaneously;
  • export data from tables and queries selected from different databases;
  • the command-line version of the utility to export data using the configuration (template) file with all export settings.

 

Q: Are there any limitations implied in the trial version as compared with the full one?

A: Actually the trial version of the utility only allows you to export 20% of records at a time. In spite of this limitation, you can test all the features implemented in Data Export for SQL Server within the 30-day trial period.

 

 

Q: What is the easiest way to configure the template files for the Data Export console application?

A: You can configure the template files for each table visually using the Data Export Wizard application. Set the required export options and select the Tools | Save Template menu item on Step 8 or Step 9 of the wizard. All the options will be saved to the template file which can be used by the console application.

 

 

Q: I work behind a firewall (router). Can EMS Data Export connect to a remote SQL Server server?

A: Yes, but to do this, you should open the port where SQL Server works (1433 by default) on your firewall and on the firewall of the remote network.

Q:How to connect to a named instance of SQL Server in EMS Data Export for SQL Server?

A:To connect to a named instance of SQL Server 2005 just enter instance name in after host name and back slash symbol in 'Host name' field at the Setting Connection Properties step. (For example: my_server\my_instance.)

To connect to a named instance of SQL Server 2000 you need:

- Run SQL Server Client Network Utility (WINDOWS\\SYSTEM32\\cliconfig.exe) on client computer where Data Export for SQL Server runs.

- Go to the second (Alias) tab of the Utility.

- Add a new server alias with Server Name in form <server_name>\\<instanse_name> and TCP/IP as Network library.

- Use the server alias name as host name in Data Export.

Q: When connecting to SQL Server I get an error "SQL Server does not exist or access denied". What is wrong?

A: Probably, your SQL Server is installed as a named instance (See Q. "How to connect to a named instance of SQL Server in EMS SQL Manager for SQL Server?").

Besides, the following factors can be the reasons for connection problems:

- You are trying to connect to SQL Server beyond your local network, through firewall (See Q. "I work behind a firewall (router). Can Data Export connect to a remote SQL Server?"

- Wrong login/password. Either you use SQL Server Authentication, but this authentication type is forbidden on the server, or you use Windows Authentication to connect to the server, but the login that corresponds to your domain name is absent on SQL Server.

- MDAC works incorrectly. Try to reinstall Microsoft Data Access Components.

- SQL Server works on a non-standard (other than 1433) port (See Q. "I can access my server via an alternative port. I have searched for a setting in the program to alter the connection port, but have not yet been able to locate this. How would I go about altering this port?".

- There are no enabled client connection protocols. Or all enabled client connection protocols are disabled on server side. Use SQL Server Client Network Utility (WINDOWS\\SYSTEM32\\cliconfig.exe) for connection to SQL Server 2000 or lower or SQL Server Configuration Manager to enable appropriate protocols.

 

Q: I can access my server via an alternative port. I have searched for a setting in EMS Data Impoert for SQL Server to alter the connection port, but have not yet been able to locate this. How would I go about altering this port?

A: To connect to SQL Server 2005 on alternative port do the following:

- Run SQL Server Configuration Manager on client computer where Data Export runs.

- Expand the SQL Native Client Configuration section.

- Select the Aliases section.

- Add a new server alias and set server name, port number and TCP/IP as Network library.

- Use the server alias name as host name in Data Export utility.

To connect to SQL Server 2000 on alternative port do the following:

- Run SQL Server Client Network Utility (WINDOWS\\SYSTEM32\\cliconfg.exe) on client computer where Data Export runs utility.

- Go to the second (Alias) tab of the Utility.

- Add a new server alias and set server name, port number and TCP/IP as Network library.

- Use the server alias name as host name in Data Export utility.

 

Scroll to top

 

 

If you still have any questions, contact us at Support Center.