HP Vertica 7.1.x MS Connectivity Pack

Connectivity Pack for Microsoft Guide
HP Vertica Analytic Database

Software Version: 7.1.x
Document Release Date: 7/21/2016
Legal Notices
Warranty
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be
construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer
Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial
license.
Copyright Notice
Copyright 2006 - 2015 Hewlett-Packard Development Company, L.P.
Trademark Notices
Adobe is a trademark of Adobe Systems Incorporated.
Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.
UNIX is a registered trademark of The Open Group.
Page 2 of 31
Contents
Contents
Introduction
Installation
System Prerequisites
Operating System
.NET Framework
Microsoft Visual Studio
Configuring BIDS or SSDT-BI Integration

Microsoft SQL Server
Downloading and Installing the Connectivity Pack
9
9
10
Downloading the HP Vertica Connectivity Pack for Microsoft
10
Installing the HP Vertica Connectivity Pack for Microsoft
11
Upgrading the Connectivity Pack
Microsoft Components
12
13
BIDS and SSDT-BI
13
SQL Server Analysis Services (SSAS) Support
13
SQL Server Integration Services (SSIS) Support
14
SQL Server Reporting Services (SSRS) Support
14
Compatibility Issues and Limitations
16
BIDS and SSDT-BI Limitations
16
SSAS Limitations
16
SSIS Limitations
16
SSRS Limitations
18
General Limitations
20
Appendix A: OLE DB Connection Properties
22
We appreciate your feedback!
31
Page 3 of 31

Introduction
Introduction
The HP Vertica Connectivity Pack for Microsoft is a package you download from HP Vertica that
allows you to integrate your HP Vertica server with an environment that includes Microsoft
components previously installed on your system. The Connectivity Pack includes the ADO.NET
and OLE DB client drivers and additional tools for integration with Microsoft Visual Studio and
Microsoft SQL Server.
Specifically, the Connectivity Pack is an enhanced .NET data provider package and provides
integration with the following Microsoft components:
l
Business Intelligence Development Studio (BIDS) for Visual Studio 2008 for use with SQL
Server 2012. BIDS is a client-based application used to develop business intelligence solutions
and based on the Microsoft Visual Studio development environment. It includes additional
project types specific to SQL Server Business Intelligence. As a developer, you can use BIDS
to develop business solutions.
SQL Server Data Tool - Business Intelligence (SSDT-BI) for Visual Studio 2010/2012 for use
with SQL Server 2012. SSDT-BI replaces BIDS for Visual Studio 2010 and 2012. It serves the
same purpose as BIDS, providing a development environment for developing business
intelligence solutions.
SQL Server Analysis Services (SSAS) for SQL Server 2008 and 2012. Use SSAS for OLAP and
data mining, while using HP Vertica as the source for cube creation.
SQL Server Integration Services (SSIS) for SQL Server 2008 and 2012. SSIS provides SQL
Server Type Mappings to map data types between HP Vertica and SQL Server. Use SSIS for
data migration, data integration and workflow, and ETL.
SQL Server Reporting Services (SSRS). Use SSRS to generate reports.
The following figure displays component relationships.
HP Vertica Analytic Database (7.1.x)
Page 4 of 31

Introduction
The HP Vertica Connectivity Pack for Microsoft is available in both 32-bit and 64-bit versions.
Download the Connectivity Pack that matches your operating system (32-bit or 64-bit).
Page 5 of 31

Installation
Installation
HP Vertica offers both client- and server-side plug-in components. You need these components to
develop and implement the Microsoft Business Intelligence capabilities.
When you download and install the HP Vertica Connectivity Pack for Microsoft and launch the
installer:
l
The installer detects the Microsoft components that are installed on your system. You choose
the integration features from the Connectivity Pack that you want to install.
If you do not have a version of Visual Studio or SQL Server installed on your system,you do not
have the option of installing the Connectivity Pack features associated with those Microsoft
products.
If you have neither Visual Studio nor SQL Server on your system, the installer installs only the
ADO.NET and OLE DB drivers. In this case, other optional contents within the Connectivity
Pack are not visible when you install.
The Vertica Data Provider - InstallShield Wizard displays only those items related to the Microsoft
products already installed on your system.
If you are installing on a system that includes all of the Microsoft components, the following items
are pre-selected during installation. Review the list, and deselect those items that you do not want
to install.
SQL Server 2008 Integration
SQL Server Analysis Services Integration 64 bit
SQL Server Type Mappings
Page 6 of 31

Installation
SQL Server Reporting Services 64 bit

SQL Server 2012 Integration
SQL Server Analysis Services Integration 64 bit
SQL Server Type Mappings
SQL Server Reporting Services 64 bit
Visual Studio 2008 Shell Integration
Business Intelligence Development Studio Integration
SQL Server Data Tool Integration
SQL Server Data Tool Integration
ADO.NET Driver
OLE DB 32-bit Driver
OLE DB 64-bit Driver
System Prerequisites
The HP Vertica Microsoft Connectivity Pack released with HP Vertica Release 7.0 or later has
basic system prerequisite requirements. The pack also requires that specific Microsoft components
be installed for full integration.
For a list of all prerequisites, see the Supported Platforms document located at
http://www.vertica.com/documentation.
Operating System
The HP Vertica Connectivity Pack for Microsoft 7.1.x requires a supported Windows operating
system. You can find the list of supported Windows versions in the Supported Platforms document
a http://www.vertica.com/documentation.
.NET Framework
The .NET framework is not bundled into the HP Vertica Connectivity Pack for Microsoft. However,
during Connectivity Pack installation, a web installer launches if Microsoft .NET 3.5 SP1 is not
detected on your system. You then have the opportunity to download the framework. Also, if your
operating system version includes .NET 3.5 SP1, but it is not turned on, the installer turns on the
feature.
You can find the requirements for the .NET framework for the HP Vertica Connectivity Pack for
Microsoft in the Supported Platforms document at http://www.vertica.com/documentation.
If you have Visual Studio 2010 or 2012 installed, your system already includes Microsoft .NET
Framework 4.0 or 4.5, respectively. You also need Microsoft .NET 3.5 SP1 to use the HP Vertica
Connectivity Pack for Microsoft integration features.
Page 7 of 31

Installation
Use the following links to download the appropriate version of .NET framework directly from
Microsoft:
l
For .NET Framework 3.5 SP1:

http://www.microsoft.com/en-us/download/details.aspx?id=22
For .NET Framework 4.0:

For .NET Framework 4.5:

Microsoft Visual Studio

The HP Vertica Microsoft Connectivity Pack installer provides a Visual Studio plug-in called Visual
Studio <version> Shell Integration. This plug-in allows you to use HP Vertica as a Visual Studio
Data Source for Visual Studio 2008, 2010, or 2012. For Visual Studio 2012, you can use the
Ultimate, Premium, or Professional editions.The connection properties for the plug-in are the same
as ADO.NET connection properties.
Important: You must have Visual Studio and the appropriate SDK installed to use the Visual
Studio plug-in.
After the plug-in is installed, you can use it to access your HP Vertica database from within Visual
Studio. If you do not have the SDK installed, download the SDK specific to your version of Visual
Studio.
l
For the Microsoft Visual Studio 2008 SDK:

For the Microsoft Visual Studio 2008 SP1 SDK:


For the Microsoft Visual Studio 2010 SP1 SDK:
Page 8 of 31

Installation
l

Configuring BIDS or SSDT-BI Integration

The HP Vertica Microsoft Connectivity Pack installer provides BIDS (Visual Studio 2008) or SSDTBI (Visual Studio 2010 or 2012) integration. To use BIDS or SSDT-BI:
1. Install the BIDS or SSDT-BI development tool add-on for Visual Studio.
2. Verify that SQL Server is installed on the same or a different machine.
3. Verify that the SQL Server Shared Features for BIDS or SSDT-BI have been activated.
4. Verify that the HP Vertica Microsoft Connectivity Pack has been installed.
You can then develop packages using BIDS or SSDT-BI, creating your projects using SQL Servers
SSIS, SSAS, SSRS features. To use these features, you must be connected to HP Vertica through
the HP Vertica ADO.NET driver (for SSIS and SSRS) or the OLE DB driver (SSAS).
Microsoft SQL Server

Use SQL Server 2008 or 2012. The HP Vertica Connectivity Pack for Microsoft installer provides
an enhanced HP Vertica .NET data-provider that enables support for the following:
l
SQL Server 2008 and 2012:

SQL Server Integration Services (SSIS)
SQL Server Reporting Services (SSRS)
SQL Server Analysis Services (SSAS)
SQL Server using Visual Studio 2008 Business Intelligence Development Studio (BIDS)
SQL Server using Visual Studio 2010 and 2012 SQL Server Data Tool - Business
Intelligence (SSDT-BI)
Note: For SQL Server 2012, you can use either SQL Server 2012 or SQL Server 2012 SP1.
Page 9 of 31

Installation
To use the enhanced HP Vertica.NET data provider, you must install SQL Server first. Then, you
can install the Connectivity Pack for Microsoft. The following components must be installed on the
SQL server:
For...
Install...
SSAS
The Analysis Services Instance Feature.
SSRS
The Reporting Services Instance Feature.
SSIS (Data Type Mappings)
The SQL Server Integration Services Shared Feature.
BIDS (for Visual Studio 2008)
Business Intelligence Development Studio Shared

Feature only after installing Microsoft Visual Studio
2008.
SSDT-BI (Visual Studio 2010 or 2012)
SQL Server Data Tool - Business Intelligence Shared

Feature only after installing Microsoft Visual Studio
2010 or 2012.
Downloading and Installing the Connectivity Pack

This topic details how to download and install the HP Vertica Microsoft Connectivity Pack for
Windows systems.
Read System Prerequisites before you proceed.
Downloading the HP Vertica Connectivity Pack for

Microsoft
Both 32-bit and 64-bit installers are available. Use the correct installer for your operating system.
1. Open a Web browser, and log in to the myVertica portal.
2. Click the Download tab, and select the HP Vertica Microsoft Connectivity Pack installer that
you want to install.
3. Follow the on-screen prompts to download the installer.
Page 10 of 31

Installation
Installing the HP Vertica Connectivity Pack for

Microsoft
1. As the Windows Administrator, double-click the installer (either vertica-cp-7.1.x-0.64.exe or
vertica-cp-7.1.x-0.32.exe) to start the install process.
2. When the introduction screen appears, click Next to begin the installation.
3. [Optional] Change the installation directory, and click Next. The default directory is C:\Program
Files\Vertica Systems\.
n
You must have the appropriate Visual Studio SDK on your system to use the integration
pack features for Visual Studio (such as using the HP Vertica plug-in).
If the SDK is not detected on your system during installation, you are prompted with two
choices:
o
Continue installation without the SDK (if you do not plan to use Visual Studio integration
features)
Stop installation and install the appropriate Visual Studio SDK
4. Verify that the integration features you want to install are selected, and click Next.
n
Features automatically selected for installation depend on which Microsoft components are
already installed on the server.
Whether features appear as options during installation depends upon the Microsoft
components installed on your server.
If the prerequisite software is not installed, then the additional Connectivity Pack features
are not shown. See System Prerequisites for details on optional prerequisites for the HP
Vertica Microsoft Connectivity Pack.
5. Click Install to install the options you selected.

6. Click Finish.
Note:The ADO.NET and OLE DB drivers are installed, respectively, in the ADO.NET and OLE
DB folders of the installation folder. The ADO.NET driver is also installed into the Windows
Global Assembly Cache (GAC).
Page 11 of 31

Installation
Upgrading the Connectivity Pack

As of HP Vertica Release 7.0, you no longer need to uninstall previous versions of the ADO.NET
driver before installing the new HP Vertica Microsoft Connectivity Pack. The installer automatically
uninstalls previous versions of the ADO.NET driver and installs the newest version.
Note: Sometimes, you may want to install the SSAS, SSIS, or SSRS components on a server
contains more than one instance of SQL Server. In such cases, the installer places the
Connectivity Pack integration components on the last instance of SQL Server, based on the
order in the Windows registry.
Page 12 of 31

This section describes the Microsoft Business Intelligence components you can use with Microsoft
Visual Studio and Microsoft SQL Server. After configuration, you can use these Microsoft
components to develop business solutions using your HP Vertica server.
BIDS and SSDT-BI

Business Intelligence Development Studio (BIDS) is MicrosoftVisual Studio 2008 with additional
project types that are specific to SQL Server business intelligence. BIDS is the primary
environment that you use to develop business solutions that include Analysis Services, Integration
Services, and Reporting Services projects.
SQL Server Data Tool - Business Intelligence (SSDT-BI) replaces BIDS for Visual Studio 2010 and
2012. It serves the same purpose as BIDS, providing a development environment for developing
business solutions.
Note: Always use the HP Vertica ADO.NET driver when connecting to the HP Vertica server
from BIDS or SSDT-BI.
Both BIDS and SSDT-BI are client-based applications that include additional project types specific
to SQL Server Business Intelligence.
You can use the Visual Studio Shell Integration plug-in to browse a database from within the Visual
Studio Server Explorer. This capability allows you to work outside of BIDS or SSDT-BI
development to perform tasks, such as listing tables or inserting data. When you use Visual Studio
in BIDS or SSDT-BI mode, you can develop business solutions using the data in your HP Vertica
database. For example,you can create cubes or open tables.
Microsoft does not support following configurations:
l
You cannot use Microsoft Visual Studio 2008 with BIDS development to create a SQL Server
2012 Business Intelligence solution.
You cannot use Microsoft Visual Studio 2010/2012 with SSDT-BI development to create a SQL
Server 2008 Business Intelligence solution.
SQL Server Analysis Services (SSAS) Support

BIDS or SSDT-BI includes the Analysis Services project for developing online analytical
processing (OLAP) for business intelligence applications. This project type includes templates for:
Page 13 of 31

Cubes
Dimensions
Data sources
Data source views
It also provides the tools for working with these objects.

Note: Always use the HP Vertica OLE DB driver when connecting to the HP Verticaserver
from SSAS.
You can find the OLE DB connection properties in Appendix A: OLE DB Connection Properties.
SQL Server Integration Services (SSIS) Support

BIDS or SSDT-BI includes the Integration Services project for developing ETL solutions. This
project type includes templates for:
l
Packages
Data sources
Data source views
It also provides the tools for working with these objects.

You can find support for using HP Vertica as a data source and target from both SSIS and the
import/export wizard. You must install mapping files specific to HP Vertica on the Integration
Server and BIDS or SSDT-BI workstation to enable this capability. The HP Vertica Microsoft
Connectivity Pack installs these mapping files as the "SQL Server Type Mappings" component(s)
in both 32-bit and 64-bit versions.
Note: Always use the HP Vertica ADO.NET driver when connecting to the HP Vertica server
from SSIS.
SQL Server Reporting Services (SSRS) Support

BIDS or SSDT-BI includes Report projects for developing reporting solutions.
Page 14 of 31

You can use HP Vertica as a data source for Reporting Services. The installer implements various
configuration file modifications to enable this capability on both the BIDS or SSDT-BI workstation
and the Reporting Services server.
Page 15 of 31


This section lists compatibility issues and limitations for Connectivity Pack integration with
Microsoft Visual Studio and Microsoft SQL Server.
BIDS and SSDT-BI Limitations

BIDS and SSDT-BI not designed to run on Itanium 64-bit
BIDS and SSDT-BI are 32-bit development environments for Analysis Services, Integration
Services, and Reporting Services projects. They are not designed to run on the Itanium 64-bit
architecture and thus are not installed on Itanium servers.
SSAS Limitations
Restart SSAS after installing the HP Vertica Microsoft Connectivity Pack
If, after installing the HP Vertica Microsoft Connectivity Pack, an SSAS cube build fails, restart the
SSAS service.
Tabular Model not supported
The SSAS Tabular Model is not supported.
SSIS Limitations
Data Type Limitations
Consider the following data type limitations when using SQL Server Integration Services (SSIS).
l
Transferring Time Data

When transferring time data, SSIS uses the TimeSpan data type that supports precision greater
than six digits. The HP Vertica ADO.NET driver translates TimeSpan as an Interval data type
that supports up to six digits. The Interval type is not converted to the TimeSpan type during
transfer. As a result, if the time value has a precision of more than six digits, the data is
truncated, not rounded.
For information on ADO.NET data types, refer to ADO.NET Data Types.
DATE and DATETIME
Page 16 of 31

To function without errors, DATE and DATETIME range falls is from 0001-01-01
00:00:00.0000000 to 9999-12-31 23:59:59.999999.
In SSIS, the DATETIME type (DT_TIMESTAMP) supports only a scale up to three decimal
places for the seconds. Any decimal places after that are automatically discarded. You can
perform derived column transformations only on DATETIME values between January 1, 1753
through December 31, 9999.
l
Numeric
The maximum and minimum decimal allowed is:
Max: +79,228,162,514,264,337,593,543,950,335
Min: -79,228,162,514,264,337,593,543,950,335
For example, if the scale is 16, the range of values is:
+/- 7,922,816,251,426.4337593543950335
The valid scale range is any number that is smaller than 29 and greater than 38. Using a scale
between 29 and 38 does not generate an error.
See : http://msdn.microsoft.com/en-us/library/system.decimal.maxvalue.aspx
Character
The CHAR and VARCHAR data types used in SSIS is DT_WSTR, with a maximum length of
4000 characters.
In SSIS, HP Vertica strings are converted to Unicode strings in SSIS to handle multi-lingual
data. You can convert these strings to ASCII using a Data Conversion Task.
Floating Point
SQL Server does not support NaN, Infinity, or Infinity values. These values are supported
when you use SSIS to transfer between HP Vertica instances, but they are not supported with a
SQL Server Destination.
Scale
Whenever you use a scale greater than 38, SSIS replaces it with a value of 4.
Interval
Page 17 of 31

SSIS does not support interval types. It converts them to TIME and strips off the day
component. Any package that has interval types greater than a day returns incorrect results.
Data Mapping when Using the SQL Server Import and Export Wizard
When you create an Integrated Services package (SSIS) using the SQL Server Import and Export
Wizard, certain data types do not automatically map correctly. A mapping issue can occur when
you use the wizard with:
l
SQL Server Native OLE DB Provider for SQL Server 2008 or 2012
SQL Server Native Client 10.0/11.0 Provider for SQL Server 2010/2012
To avoid this issue, you can manually change the type mappings using either BIDS or SSDT-BI.
Data Transfer of Certain Data Types
When using an Integrated Services package (SSIS) with the SQL Server OLE DB Provider for SQL
Server 2008 or 2012, certain data type transfers can fail when transferring from HP Vertica to SQL
Server. To avoid this issue, use either BIDS or SSDT-BI when transferring data.
Batch Insert of Varbinary or Long Varbinary Data Types
Sometimes, one row of a batch insert of varbinary or long varbinary data types exceeds the data
type limit:
l
Varbinary 65 KB
Long Binary 32 MB
In such cases, all rows are rejected, rather than just the one row whose length exceeds the type
limit. The batch insert fails with the message "row(s) are rejected".
To avoid this issue, use a predicate to filter out rows from the source that do not fit into the receiving
database.
Boolean Queries in SQL Server Query Designer
When issuing a Boolean query in SQL Server Query Designer, you must enclose Boolean column
values in quotes. Otherwise, you receive a SQL execution error (for example, someboolean =
'true').
SSRS Limitations
Data Connection Wizard Workaround
Page 18 of 31

The SSRS Report Wizard provides a data connection wizard. After you select the wizard and enter
all the connection information, the OK button is not clickable. You cannot save your work and
continue. The workaround is not to use the wizard and to use the following panel instead.
Report Wizard - Query Designer

The HP Vertica Data Provider uses the Report Wizard's Generic Query Designer. Other data
sources use a Graphical Query Designer that supports visually building queries. The Graphical
Query Designer is a part of a package call Visual Data Tools (VDT). The Graphical Query Designer
works only with Generic OLE DB providers and the built-in providers. You cannot use it with the HP
Vertica Data Provider.
Report Builder
Report Builder is a web-based report design tool. It does not support creating reports using custom
data extensions, so you cannot use it with the HP Vertica Data Provider. When you create a report
using Report Builder, existing HP Vertica data sources appear in the list of available data sources.
However, choosing an HP Vertica data source causes an error.
Schema Name not Automatically Provided when Mapping HP Vertica Destination
Currently, when you map an HP Vertica destination, the schema name is not automatically
provided. You must enter it manually or pick it from the drop-down menu as follows.
Page 19 of 31

General Limitations
Visual Studio 2012 May Need Update 3
You may need to install update 3 to Visual Studio 2012 if:
l
You launch Server Explorer to view and work with your HP Vertica server, but the HP Vertica
data source is not visible.
You create a SSAS cube, connect to HP Vertica, and find either an empty list of tables or tables
not functioning correctly.
This issue does not occur for other supported versions of Visual Studio.
Results Viewer Limited to 655 Columns
The Visual Studio results viewer cannot execute a query that includes more than 655 columns. If a
table includes more than 655 columns, select specific columns (up to 655 total) rather than
selecting all columns.
Manually Refresh Settings for Visual Studio
If, after installing the HP Vertica Microsoft Connectivity Pack, you do not see HP Vertica listed as a
data provider, manually refresh.
To do so, run devenv.exe/setup, which you can find in the Visual Studio's installation folder.
SQL Pane Issues
Page 20 of 31

ALTER TABLE or CREATE TABLE

You use Visual Studio 2008, 2010, or 2012 and issue the ALTER TABLE or CREATE TABLE
statement in the SQL pane. However, a message displays telling you that the statement is not
supported. To resolve the error, click Continue, and the query executes.
Queries with Semicolons

You use Visual Studio 2008, 2010, or 2012 and execute a SQL query in the SQL pane. If you
include a semicolon (;) with your query, the query executes, but the result returned is not
editable. To avoid this issue, enter the same query in the SQL pane without the semicolon.
Page 21 of 31


Use the Connection Manager to set the OLE DB connection string properties, which define your
connection. You access the Connection Manager from within Visual Studio.
This figure shows a sample Connection page from the Connection Manager dialog box.
These connection parameters appear on the Connection page.

Parameters
Action
Default Value
Provider
Select the native OLE DB
None
provider for the connection.

OLE DB Provider
Indicates Vertica OLE DB
None
Provider.
Server or file name
Enter the server or file name.
None
Location
Not supported.
Disabled.
Page 22 of 31

Parameters
Action
Default Value
Use Windows NT Integrated
Not supported.
Disabled.
Security
Use a specific user name and Enter a user name and
password
None
password.
Connect with No Password:
Select the Blank password
check box.
Save and Encrypt Password:
Select Allow saving password.
Initial Catalog
The name of the database
None
running on the server.

A sample All page from the Connection Manager dialog box follows. The All page includes all
possible connection string properties for the provider.
Page 23 of 31

The table that follows lists the connection parameters for the All page.
For OLE DB properties information specific to Microsoft, see the Microsoft documentation OLE DB
Properties.
Page 24 of 31

Parameters
Action
Default Value
Extended Properties
Not supported.
Leave blank. Do not

set this field.
Locale Identifier
Indicates the Locale ID.
Mode
Specifies access permissions.
Connect Timeout
Not supported. The value can be set,
but has no effect.

General Timeout
but has no effect.

File Name
Blank
but has no effect.

OLE DB Services
Specifies which OLE DB services to
Default
enable or disable.
Password
Specifies the password for the User ID.
None
For no password, insert an empty
(If no password
string.
specified, login
succeeds only if the
user has not set a
password.)
Persist Security Info
A security measure. When False,
True
security sensitive-information, such as

the password, is not returned as part of
the connection if the connection is open
or has ever been in an open state.
User ID
The database username.
None
Page 25 of 31

Parameters
Action
Default Value
Data Source
The host name or IP address of any
None
active node in an HP Vertica cluster.

You can provide an IPv4 address, IPv6
address, or hostname.
In mixed IPv4/IPv6 networks, the DNS
server configuration determines which
IP version address is sent first. Use the
PreferredAddressFamily option to
force the connection to use either IPv4
or IPv6.
Initial Catalog
The name of the database running on
None
the server.
Provider
The name of the OLE DB Provider to
VerticaOLEDB.1
use when connecting to the Data

Source.
BackupServerNode
A designated host name or IP address
None
to use if the ServerName host is

unavailable. Enter as a string.
Connection attempts continue until
successful or until the list of server
nodes is exhausted.
Valid values:Comma-separated list of
servers optionally followed by a colon
and port number. For example:
server1:5033,server2:5034
Page 26 of 31

Parameters
Action
Default Value
ConnectionLoadBalance
A Boolean value that determines
False
whether the connection can be

redirected to a host in the database
other than the ServerNode.
This parameter affects the connection
only if load balancing is set to a value
other than NONE. When the node
differs from the node that the client is
connected to, the client disconnects
and reconnects to the targeted node.
See About Native Connection Load
Balancing in the Administration Guide.
ConnSettings
SQL commands that the driver should
None
execute immediately after connecting

to the server. Use to configure the
connection, such as setting a schema
search path.
Reserved symbol:';' To set multiple
parameters in this field use '%3B' for ','.
Spaces: Use '+'.
Page 27 of 31

Parameters
Action
Default Value
DirectBatchInsert
Controls where data inserted through
False
the connection is stored.

Valid Values:
l
True Data inserted directly into

ROS containers.
False Stores data using AUTO

mode.
When you load data using AUTO mode,

HP Vertica inserts the data first into the
WOS. If the WOS is full, then HP
Vertica inserts the data directly into
ROS. See the COPY statement for
more details.
KerberosHostName
Provides the instance or host name
None.
portion of the HP Vertica Kerberos

principal; for example:
vertica/host@EXAMPLE.COM
KerberosServiceName
Provides the service name portion of
None
the HP Vertica Kerberos principal; for

example: vertica/host@EXAMPLE.COM
Label
Sets a label for the connection on the
None
server. This value appears in the

session_id column of the V_
MONITOR.SESSIONS system table.
LogLevel
Specifies the amount of information
None
included in the log. Leave this field

blank or set to 0 unless otherwise
instructed by HP Vertica Customer
Support.
LogPath
The path for the log file.
None
Page 28 of 31

Parameters
Action
Default Value
Port
The port number on which HP Vertica
None
listens for OLE DB connections.
(If not set, uses port

5433.)
PreferredAddressFamily
The IP version to use if the client and
None
server have both IPv4 and IPv6

addresses and you have provided a
host name. Valid values are:
l
ipv4Connect to the server using

IPv4.
ipv6Connect to the server using

IPv6.
noneUse the IP address provided

by the DNS server.
SSLCertFile
The absolute path of the client's public
None
certificate file. This file can reside

anywhere on the system.
SSLKeyFile
The absolute path to the client's private
None
key file. This file can reside anywhere

on the system.
Page 29 of 31

Parameters
Action
Default Value
SSLMode
Controls whether the connection to the
Prefer
database uses SSL encryption. Valid

values follow.
Valid Values:
l
requireRequires the server to use

SSL. If the server cannot provide an
encrypted channel, the connection
fails.
preferPrefers that the server use

SSL. If the server does not offer an
encrypted channel, the client
requests one. The first attempt is
made with SSL. If that attempt fails,
the second attempt is over a clear
channel.
allowMakes a connection to the

server whether or not the server
uses SSL. The first attempt is made
over a clear channel. If that attempt
fails, a second attempt is over SSL.
disableNever connects to the

server using SSL. Typically, you use
this setting for troubleshooting.
Page 30 of 31
We appreciate your feedback!

If you have comments about this document, you can contact the documentation team by email. If
an email client is configured on this system, click the link above and an email window opens with
the following information in the subject line:
Feedback on Connectivity Pack for Microsoft Guide (Vertica Analytic Database 7.1.x)
Just add your feedback to the email and click send.
If no email client is available, copy the information above to a new message in a web mail client,
and send your feedback to vertica-docfeedback@hp.com.
Page 31 of 31

HP Vertica 7.1.x MS Connectivity Pack

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HP Vertica 7.1.x MS Connectivity Pack

Uploaded by

Copyright:

Available Formats

Connectivity Pack for Microsoft Guide

HP Vertica Analytic Database

Document Release Date: 7/21/2016

Restricted Rights Legend

HP Vertica Analytic Database

Microsoft Visual Studio

Configuring BIDS or SSDT-BI Integration

Downloading the HP Vertica Connectivity Pack for Microsoft

Installing the HP Vertica Connectivity Pack for Microsoft

Upgrading the Connectivity Pack

BIDS and SSDT-BI

SQL Server Analysis Services (SSAS) Support

SQL Server Integration Services (SSIS) Support

SQL Server Reporting Services (SSRS) Support

Compatibility Issues and Limitations

BIDS and SSDT-BI Limitations

Appendix A: OLE DB Connection Properties

We appreciate your feedback!

HP Vertica Analytic Database

Connectivity Pack for Microsoft Guide

SQL Server Reporting Services (SSRS). Use SSRS to generate reports.

The following figure displays component relationships.

HP Vertica Analytic Database (7.1.x)

Connectivity Pack for Microsoft Guide

HP Vertica Analytic Database (7.1.x)

Connectivity Pack for Microsoft Guide

HP Vertica Analytic Database (7.1.x)

Connectivity Pack for Microsoft Guide

SQL Server Reporting Services 64 bit

HP Vertica Analytic Database (7.1.x)

Connectivity Pack for Microsoft Guide

For .NET Framework 3.5 SP1:

For .NET Framework 4.0:

For .NET Framework 4.5:

Microsoft Visual Studio

For the Microsoft Visual Studio 2008 SDK:

For the Microsoft Visual Studio 2008 SP1 SDK:

For the Microsoft Visual Studio 2010 SDK:

For the Microsoft Visual Studio 2010 SP1 SDK:

HP Vertica Analytic Database (7.1.x)

Connectivity Pack for Microsoft Guide

For the Microsoft Visual Studio 2012 SDK:

Configuring BIDS or SSDT-BI Integration

Microsoft SQL Server

SQL Server 2008 and 2012:

SQL Server Reporting Services (SSRS)

SQL Server Analysis Services (SSAS)

HP Vertica Analytic Database (7.1.x)

Connectivity Pack for Microsoft Guide

The Analysis Services Instance Feature.

The Reporting Services Instance Feature.

SSIS (Data Type Mappings)

The SQL Server Integration Services Shared Feature.

BIDS (for Visual Studio 2008)

Business Intelligence Development Studio Shared

SSDT-BI (Visual Studio 2010 or 2012)

SQL Server Data Tool - Business Intelligence Shared

Downloading and Installing the Connectivity Pack

Downloading the HP Vertica Connectivity Pack for

HP Vertica Analytic Database (7.1.x)

Connectivity Pack for Microsoft Guide

Installing the HP Vertica Connectivity Pack for

Stop installation and install the appropriate Visual Studio SDK

5. Click Install to install the options you selected.