SQL Server Connection Parameters

Easily shred and import XML data into an SQL Server database.

This page describes the various aspects of connecting to an SQL Server database to import XML into SQL Server using Exult SQL Server. The connection parameters are entered on the connection page as shown here:

Connecting to SQL Server using Exult SQL Server for
     shredding XML to database tables.

Database Server

The location of the SQL Server is entered one of the following formats:

  • Server Hostname: When just the server hostname is entered as shown below, a connection is made to the default database instance on the specified server. The default database instance is called MSSQLSERVER.
    Connecting to default instance
  of SQL Server for shredding XML using Exult SQL Server
  • Server Hostname and Instance: To specify the instance name in addition to the SQL Server hostname, enter it with the hostname followed by the instance name separated by a backslash: Server\Instance In the example below, a connection is attempted to the instance named XDB_2012 on the server MICKEY.
    Connecting to an named
  instance of SQL Server when converting XML data using Exult SQL
  Server
  • Specifying the Port Number: When the SQL Server instance is listening on a port number different from the default (of 1433), it is necessary to specify the port number also. When SQL Server is configured for network connections via TCP/IP, by default the instance listens on a dynamic port (requesting the operating system for a free port number). You can ask your system administrator for the port number or look it up on the SQL Server machine.
    Specify the port number by appending it to the connection string separated by a comma (",") as follows: Server/Instance,Port. In the example shown, we are connecting to the instance named XDB_2012 on the server MICKEY listening on port 47788.
    Connecting to an named instance of SQL Server on a specified
  port for importing XML using Exult SQL Server
  • Using defaults: When specifying the connection string in the format listed above, any parameter can be skipped and the default will be used. For example:
    Server
    A connection is made to the default instance (named MSSQLSERVER) on the specified server. The instance is assumed to be listening on the default port of 1433.
    \Instance
    Connect to the specified instance on the default port 1433 on the local machine.
    \Instance,Port
    Specifies a connection to the named instance listening on the specified port.
    Server,Port
    Attempts connection to the default database on the specified port on the specified machine.

Firewall

When client connectivity is performed via network connections using TCP/IP, firewall rules need to be updated to allow connections to the specified port(s) on the SQL Server machine. This depends on the firewall being used on the SQL Server machine, but when using the Windows firewall, here are the instructions to allow client connections to SQL Server.

Authentication Method

An SQL Server database might be configured for supporting client connections with the following authentication modes:

Using Windows Authentication
When a user connects using Windows Authentication, SQL Server validates the Windows account name and password using the Windows principal token in the operating system. This means that the user identity is confirmed by the Windows operating system.. SQL Server does not ask for the password, and does not perform the identity validation itself. Windows Authentication is the default authentication mode and uses Kerberos security protocol, provides password policy enforcement with regard to complexity validation for strong passwords, provides support for account lockout, and supports password expiration. A connection made using Windows Authentication is also called a trusted connection, because SQL Server trusts the credentials provided by Windows.
Using SQL Server Authentication
When using SQL Server Authentication, logins are created in SQL Server that are not based on Windows user accounts. Both the user name and the password are created by using SQL Server and stored in SQL Server. Users connecting using SQL Server Authentication must provide their credentials (login and password) every time that they connect. When using SQL Server Authentication, you must set strong passwords for all SQL Server accounts.

Windows Authentication

For connecting using Windows Authentication, enter the database server location, set the Authentication Method to Windows Authentication and click Connect to fetch the list of databases available. If the connection succeeds, the Databases list box is populated and the server properties are shown below.
Connect to SQL Server using
			       Windows Authentication for importing
			       XML data into SQL Server using Exult
			       SQL Server

SQL Server Authentication

After entering the database server location, set the Authentication Method to SQL Server Authentication. The username and password fields are required with this authentication method. Enter the correct values and click Connect. A connection is made to the server and the Databases list is populated along with the server properties table. If the connection succeeds, the connection parameters are saved in the registry. However, the password is not saved.
Connect to SQL Server using SQL
			       Server Authentication when importing
			       XML into SQL Server using Exult SQL
			       Server.

Databases

Once the connection parameters are entered and a connection is successfully made, the list of databases available on the instance is fetched. The databases are shown in the combo box. Select the database to convert or import XML into.
Fetching the list of available databases on SQL Server for
  shredding XML to tables using Exult SQL Server.

Database Properties

After the connection is made using the specified parameters, the instance properties are listed in the table. The following properties are available: Check the properties to ensure that the database you are shredding XML into is the correct one.

  • ComputerNamePhysicalNetBIOS
  • Edition
  • EditionID
  • EngineEdition
  • InstanceName
  • IsClustered
  • IsFullTextInstalled
  • IsIntegratedSecurityOnly
  • IsSingleUser
  • LCID
  • LicenseType
  • MachineName
  • NumLicenses
  • ProcessID
  • ProductVersion
  • ProductLevel
  • ResourceLastUpdateDateTime
  • ResourceVersion
  • ServerName
  • SqlCharSetName
  • SqlSortOrderName
  • FilestreamShareName

SQL Server Native Client

In case of connection problems, you may need to install the SQL Server Native Client software published by Microsoft. Please check here for the download and instructions for installing SQL Server Native Client.

Swift XML Converter

Query & extract XML data into Microsoft Excel (XLS), Microsoft Access (MDB or ACCDB), or CSV.

Exult Standard

Convert XML into Microsoft Excel (XLS), Microsoft Access (MDB or ACCDB), or CSV.

Exult SQL Server

Shred and import XML into SQL Server.

Exult MySQL

Import XML data into automatically created MySQL tables.

Exult Oracle

Import XML into Oracle.