README
DataDirect Technologies
DataDirect Connect64 for SSIS
Release 1.0.1
August 2007
CONTENTS
Available Data Providers
Notes, Known Problems, and Restrictions
Installed Files
Third-Party Vendor License Agreements
Available Data Providers
32-bit
------
DB2 Wire Protocol (IVSSISDB201.DLL)
Oracle Wire Protocol (IVSSISORA01.DLL)
Sybase Wire Protocol (IVSSISASE01.DLL)
64-bit
------
DB2 Wire Protocol (DDSSISDB201.DLL)
Oracle Wire Protocol (DDSSISORA01.DLL)
Sybase Wire Protocol (DDSSISASE01.DLL)
Notes, Known Problems, and Restrictions
The following are notes, known problems, and restrictions with Release
1.0.1 of DataDirect Connect64 for SSIS.
DB2 Data Type Mappings in the SSIS Wizard
-----------------------------------------
A known problem exists with transferring data from DB2 to Microsoft SQL
Server. Because of an issue in the SSIS Import/Export Wizard, the
Wizard does not automatically map certain DB2 columns to data types.
This section of the Wizard is described in Step 14 of Chapter 2 of the
DATADIRECT CONNECT64 FOR SSIS USER'S GUIDE. The correct mapping of data
types between DB2 and Microsoft SQL Server is as follows:
DB2 ---> SQL Server
--- ----------
real real
float float
double float
time smalldatetime
date smalldatetime
Verify that you have mapped these data types correctly on the Column
Mappings window of the Wizard.
In addition, when transferring data from Microsoft SQL Server to DB2,
data types are automatically mapped as follows:
SQL Server ---> DB2
---------- ---
binary varchar(8000) for bit data
varbinary varchar(8000) for bit data
varchar varchar(8000)
smalldatetime timestamp
8000 is the largest length that can be specified in Microsoft SQL
Server. Truncation errors and lost data are unlikely when the column is
set to this maximum value; however, if you do not need this maximum value,
performance is improved if you override it with a smaller value. You
must click the Edit SQL button on the Column Mappings window and change
the length value in the Create statement. In addition, smalldatetime
columns are mapped to timestamp to insure that no data is lost on
transfer. You can, however, map these columns to either date or time
data types if you only want that type of data to be transferred.
Data Type Mappings in Tools Other Than the SSIS Wizard
------------------------------------------------------
SSIS tools other than the Import/Export Wizard do not automatically map data
types correctly for any database. If you are using other SSIS tools,
you must verify that data types are mapped correctly for the database
you are using. In the OLE DB Destination Editor, for example, you must
correctly map data types in the Create Table window.
Stored Procedures with DB2 and Oracle
-------------------------------------
The DB2 and Oracle data providers do not support using the SQL command
of OLE DB Source to call a stored procedure. This is because DB2 and
Oracle databases are unable to describe the result sets that are
returned from a stored procedure.
Parameter Discovery
-------------------
Parameter discovery for parameter markers in a SQL command for Oracle
and Sybase is accomplished as follows. For Sybase, this happens when
OptimizePrepare is set to 0, or when OptimizePrepare is set to 1 and
the SQL statement does not include parameters for text or image columns.
For Oracle, all parameters for Select statements are described with a data
type of VARCHAR; for Insert/Update/Delete statements, the parameters are
described as the actual Oracle data types on the Oracle server.
DB2 supports parameter discovery except with DB2 UDB v7.x.
DataDirect Connect64 Configuration Manager for SSIS
---------------------------------------------------
On some systems, the Configuration Manager may crash when configuring data
sources.
As a workaround, modify the default data sources located in
C:\Documents and Settings\login_name\My Documents\DataDirect\SSISDataSources
with a text editor. The first section of the file,
[Provider], contains information specific to the provider in use. This
information can be obtained from the default data sources. The next section,
[DSNInfo], contains a brief description
of the data source. In the last section, [Properties], you can
specify provider string attributes as documented in the DataDirect Connect64 for
SSIS User's Guide and Reference.
The following example shows a sample data source for the Sybase provider:
ProviderName=DataDirect SSIS OLE DB Provider for Sybase
clsid={53575986-DD64-dd11-96E7-08844CAF800B}
[DSNInfo]
Description=My Sybase Account
[Properties]
ApplicationName=
ArraySize=100
AuthenticationMethod=0
Charset=
ConnectionRetryCount=0
ConnectionRetryDelay=3
Database=
EnableQuotedIdentifiers=0
EncryptionMethod=0
HostNameInCertificate=
InitializationString=
InterfacesFile=
InterfacesFileServerName=
Language=
LogonID=
NetworkAddress=
OptimizePrepare=1
PacketSize=0
ReportCodePageConversionErrors=0
SelectMethod=1
ServicePrincipalName=
TrustStore=
TrustStorePassword=
ValildateServerCertificate=
WorkStationID=
Installed Files
If the installer does not find a Microsoft SQL Server installation,
it displays an error. If this occurs, refer to the README.TXT file
in the \MAPPINGFILES directory.
Setup copies the following files and subdirectories to the product
installation directory:
ICULICENSE.TXT License agreement for ICU
SSISREADME.TXT This file
SSISFIXES.TXT A text file that lists the fixes in the release
\BIND:
DDODBC_LUW.lst DB2 list files for Linux/UNIX/Windows
DDOC510A.bnd
DDOS510A.bnd
DDOR510A.bnd
DDOU510A.bnd
DDON510A.bnd
DDOC510B.bnd
DDOS510B.bnd
DDOR510B.bnd
DDOU510B.bnd
DDON510B.bnd
DDOC510C.bnd
DDOS510C.bnd
DDOR510C.bnd
DDOU510C.bnd
DDON510C.bnd
\HELP:
HELP.HTM HTML help system entry file
\*.* Support folders for the HTML help system
\MAPPINGFILES
NOTE: The following .XML files are also copied to
\90\DTS\MappingFiles if such a directory
exists.
DD_SQLClientToDB2.XML Data Type Mapping File
DD_SQLClientToOracle.XML Data Type Mapping File
DD_OracletoSQLClient.XML Data Type Mapping File
DD_SQLClientToSybase.XML Data Type Mapping File
DD_SybasetoSQLClient.XML Data Type Mapping File
README.TXT Readme file for mapping files
\PROVIDERS:
For the following files, resource files for a provider end in R.DLL.
DDEXTWIN.EXE
DDSSISASE01.DLL 64-bit Sybase Wire Protocol provider
DDSSISASE01R.DLL
DDSSISDB201.DLL 64-bit DB2 Wire Protocol provider
DDSSISDB201R.DLL
DDSSISORA01.DLL 64-bit Oracle Wire Protocol provider
DDSSISORA01R.DLL
DDSSIS.LIC 64-bit provider license file
DDSSISCRYPTO01.DLL 64-bit SSL Support Library
DDSSISICU01.DLL 64-bit Unicode conversion tables
DDSSISSSL01.DLL 64-bit SSL Library
IVSSISASE01.DLL 32-bit Sybase Wire Protocol provider
IVSSISASE01R.DLL
IVSSISDB201.DLL 32-bit DB2 Wire Protocol provider
IVSSISDB201R.DLL
IVSSISORA01.DLL 32-bit Oracle Wire Protocol provider
IVSSISORA01R.DLL
IVSSIS.LIC 32-bit provider license file
IVSSISCRYPTO01.DLL 32-bit SSL Support Library
IVSSISICU01.DLL 32-bit Unicode conversion tables
IVSSISSSL01.DLL 32-bit SSL Library
\TOOLS:
DDPROCINFO.EXE Processor Information utility
MFC42.DLL C Runtime Library
MSVCRT.DLL C Runtime Library
SSISADMIN.EXE SSIS Configuration Utility
SSISADMINR.DLL Resource DLL for Configuration Utility
REMOVE.REG [Only on 64-bit installations]
Third-Party Vendor License Agreements
This DataDirect product includes ICU Version 3.2 which is subject to
the following license agreement:
ICU License - ICU 1.8.1 and later ICU License - ICU 1.8.1 and later
COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 1995-2003 International Business Machines Corporation and
others. All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, and/or sell copies of the Software, and to permit persons
to whom the Software is furnished to do so, provided that the above
copyright notice(s) and this permission notice appear in all copies of
the Software and that both the above copyright notice(s) and this
permission notice appear in supporting documentation.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL
INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING
FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Except as contained in this notice, the name of a copyright holder
shall not be used in advertising or otherwise to promote the sale, use
or other dealings in this Software without prior written authorization
of the copyright holder.
---------------------------------------------------------------------
All trademarks and registered trademarks mentioned herein are the
property of their respective owners.
---------------------------------------------------------------------
This product includes the OpenSSL Library which is subject to the
following license agreements:
OpenSSL License
Copyright (c) 1998-2006 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this
software must display the following acknowledgment:
"This product includes software developed by the OpenSSL Project for
use in the OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used
to endorse or promote products derived from this software without
prior written permission. For written permission, please contact
openssl-core@openssl.org.
5. Products derived from this software may not be called "OpenSSL"
nor may "OpenSSL" appear in their names without prior written
permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following
acknowledgment:
"This product includes software developed by the OpenSSL Project for
use in the OpenSSL Toolkit (http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS" AND ANY
EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
========================
This product includes cryptographic software written by Eric Young
(eay@cryptsoft.com). This product includes software written by
Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License
-----------------------
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
All rights reserved.
This package is an SSL implementation written by Eric Young
(eay@cryptsoft.com). The implementation was written so as to
conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as
the following conditions are aheared to. The following conditions
apply to all code found in this distribution, be it the RC4, RSA,
lhash, DES, etc., code; not just the SSL code. The SSL documentation
included with this distribution is covered by the same copyright terms
except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in
the code are not to be removed. If this package is used in a product,
Eric Young should be given attribution as the author of the parts of
the library used. This can be in the form of a textual message at
program startup or in documentation (online or textual) provided
with the package.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this
software must display the following acknowledgement:
"This product includes cryptographic software written by Eric Young
(eay@cryptsoft.com)"
The word 'cryptographic' can be left out if the routines from the
library being used are not cryptographic related :-).
4. If you include any Windows specific code (or a derivative thereof)
from the apps directory (application code) you must include an
acknowledgement:
"This product includes software written by Tim Hudson
(tjh@cryptsoft.com)"
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The licence and distribution terms for any publically available
version or derivative of this code cannot be changed. i.e. this
code cannot simply be copied and put under another distribution
licence [including the GNU Public Licence.]
~~~~~~~~~~~~~~
End of README