Amazon S3 XML File ODBC DriverAmazon S3 XML File Connector can be used to read XML Files stored in AWS S3 Buckets. Using this you can easily integrate AWS S3 XML File data. It's supports latest security standards, and optimized for large data files. It also supports reading compressed files (e.g. GZip /Zip). In this article you will learn how to quickly and efficiently integrate Amazon S3 XML File data in ODBC without coding. We will use high-performance Amazon S3 XML File Connector to easily connect to Amazon S3 XML File and then access the data inside ODBC. Let's follow the steps below to see how we can accomplish that! Amazon S3 XML File ODBC Driver is based on ZappySys Amazon S3 XML Driver which is part of ODBC PowerPack. It is a collection of high-performance ODBC drivers that enable you to integrate data in SQL Server, SSIS, a programming language, or any other ODBC-compatible application. ODBC PowerPack supports various file formats, sources and destinations, including REST/SOAP API, SFTP/FTP, storage services, and plain files, to mention a few. |
Connect to Amazon S3 XML File in other apps
|
Create ODBC Data Source (DSN) based on ZappySys Amazon S3 XML Driver
Step-by-step instructions
To get data from Amazon S3 XML File using ODBC we first need to create a DSN (Data Source) which will access data from Amazon S3 XML File. We will later be able to read data using ODBC. Perform these steps:
-
Download and install ODBC PowerPack.
-
Open ODBC Data Sources (x64):
-
Create a User data source (User DSN) based on ZappySys Amazon S3 XML Driver
ZappySys Amazon S3 XML Driver-
Create and use User DSN
if the client application is run under a User Account.
This is an ideal option
in design-time , when developing a solution, e.g. in Visual Studio 2019. Use it for both type of applications - 64-bit and 32-bit. -
Create and use System DSN
if the client application is launched under a System Account, e.g. as a Windows Service.
Usually, this is an ideal option to use
in a production environment . Use ODBC Data Source Administrator (32-bit), instead of 64-bit version, if Windows Service is a 32-bit application.
-
Create and use User DSN
if the client application is run under a User Account.
This is an ideal option
-
Create and configure a connection for the Amazon S3 storage account.
-
You can use select your desired single file by clicking [...] path button.
mybucket/dbo.tblNames.xmldbo.tblNames.xml
----------OR----------You can also read the multiple files stored in Amazon S3 Storage using wildcard pattern supported e.g. dbo.tblNames*.xml.
Note: If you want to operation with multiple files then use wild card pattern as below (when you use wild card pattern in source path then system will treat target path as folder regardless you end with slash) mybucket/dbo.tblNames.xml (will read only single .XML file) mybucket/dbo.tbl*.xml (all files starting with file name) mybucket/*.xml (all files with .xml Extension and located under folder subfolder)
mybucket/dbo.tblNames*.xml
----------OR----------You can also read the zip and gzip compressed files also without extracting it in using Amazon S3 XML Source File Task.
mybucket/dbo.tblNames*.gz -
Now select/enter Path expression in Path textbox to extract only specific part of XML string as below ($.value[*] will get content of value attribute from XML document. Value attribute is array of XML documents so we have to use [*] to indicate we want all records of that array)
NOTE: Here, We are using our desired filter, but you need to select your desired filter based on your requirement. Navigate to the Preview Tab and let's explore the different modes available to access the data.
-
--- Using Direct Query ---
Click on Preview Tab, Select Table from Tables Dropdown and select [value] and click Preview.
-
--- Using Stored Procedure ---
Note : For this you have to Save ODBC Driver configuration and then again reopen to configure same driver. For more information click here.
Click on the Custom Objects Tab, Click on Add button and select Add Procedure and Enter an appropriate name and Click on OK button to create.
-
--- Without Parameters ---
Now Stored Procedure can be created with or without parameters (see example below). If you use parameters then Set default value otherwise it may fail to compilation)
-
--- With Parameters ---
Note : Here you can use Placeholder with Paramters in Stored Procedure. Example : SELECT * FROM $ WHERE OrderID = '<@OrderID, FUN_TRIM>' or CustId = '<@CustId>' and Total >= '<@Total>'
-
-
--- Using Virtual Table ---
Note : For this you have to Save ODBC Driver configuration and then again reopen to configure same driver. For more information click here.
ZappySys APi Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.
Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 Buckets with slight variations you can create virtual tables with just URL as Parameter setting).
vt__Customers DataPath=mybucket_1/customers.xml vt__Orders DataPath=mybucket_2/orders.xml vt__Products DataPath=mybucket_3/products.xml
-
Click on the Custom Objects Tab, Click on Add button and select Add Table and Enter an appropriate name and Click on OK button to create.
-
Once you see Query Builder Window on screen Configure it.
-
Click on Preview Tab, Select Virtual Table(prefix with vt__) from Tables Dropdown or write SQL query with Virtual Table name and click Preview.
-
Click on the Custom Objects Tab, Click on Add button and select Add Table and Enter an appropriate name and Click on OK button to create.
-
-
Click OK to finish creating the data source
-
That's it; we are done. In a few clicks we configured the to Read the Amazon S3 XML File data using ZappySys Amazon S3 XML File Connector
Conclusion
In this article we showed you how to connect to Amazon S3 XML File in ODBC and integrate data without any coding, saving you time and effort. It's worth noting that ZappySys Amazon S3 XML Driver allows you to connect not only to Amazon S3 XML File, but to any Java application that supports JDBC (just use a different JDBC driver and configure it appropriately).
We encourage you to download Amazon S3 XML File Connector for ODBC and see how easy it is to use it for yourself or your team.
If you have any questions, feel free to contact ZappySys support team. You can also open a live chat immediately by clicking on the chat icon below.
Download Amazon S3 XML File Connector for ODBC Documentation
More integrations
Other connectors for ODBC
Other application integration scenarios for Amazon S3 XML File
How to connect Amazon S3 XML File in ODBC?
How to get Amazon S3 XML File data in ODBC?
How to read Amazon S3 XML File data in ODBC?
How to load Amazon S3 XML File data in ODBC?
How to import Amazon S3 XML File data in ODBC?
How to pull Amazon S3 XML File data in ODBC?
How to push data to Amazon S3 XML File in ODBC?
How to write data to Amazon S3 XML File in ODBC?
How to POST data to Amazon S3 XML File in ODBC?
Call Amazon S3 XML File API in ODBC
Consume Amazon S3 XML File API in ODBC
Amazon S3 XML File ODBC Automate
Amazon S3 XML File ODBC Integration
Integration Amazon S3 XML File in ODBC
Consume real-time Amazon S3 XML File data in ODBC
Consume real-time Amazon S3 XML File API data in ODBC
Amazon S3 XML File ODBC Driver | ODBC Driver for Amazon S3 XML File | ODBC Amazon S3 XML File Driver | SSIS Amazon S3 XML File Source | SSIS Amazon S3 XML File Destination
Connect Amazon S3 XML File in ODBC
Load Amazon S3 XML File in ODBC
Load Amazon S3 XML File data in ODBC
Read Amazon S3 XML File data in ODBC
Amazon S3 XML File API Call in ODBC