![]() |
VOOZH | about |
This guide explains everything you need to get started with the CData SSIS Components for XML. You'll learn how to install the components, activate your license, configure your first SSIS connection manager, and build a data flow task to move and transform XML data in your SQL Server Integration Services workflows.
If you are using Visual Studio 2022, the SQL Server Integration Services Projects extension must be installed.
During installation, you are prompted to activate the SSIS Component license. If you need to update or change activation:
The installer automatically prompts you to add your license. During installation, you can choose to:
To activate a full subscription license, contact the CData Orders Team and request your product key at [email protected].
Enter the license key in the installer when prompted. Once activated, the components will be licensed and ready to use inside Visual Studio without any additional steps.
When deploying SSIS packages, a Runtime Key (RTK) can also be used:
Can I use my license on multiple machines?
Yes, depending on your subscription tier. Contact [email protected] for details.
I lost my license key. How do I retrieve it?
Email [email protected] with your order number, and we'll resend your license key.
How do I transfer my license to another machine?
Yes. When transferring the license to a different machine, you will need to submit a License Transfer Request on our site linked below:
https://www.cdata.com/lic/transfer/After the License Transfer Request is submitted and successfully processed, an activation will be added to your Product Key and you will be able to activate the full license on the other machine. Once this process is finished, the license on the previous machine will be invalid.
You may also view and upgrade licenses in the self-service portal at portal.cdata.com.
Once the components are installed and licensed, you can configure a connection to XML using an SSIS Connection Manager. This Connection Manager stores all authentication and connection properties used by the Source and Destination components.
CData Drivers let you work with XML files stored locally and stored in cloud storage services like Box, Amazon S3, Google Drive, or SharePoint, right where they are.
Set the URI property to local folder path.
To connect to XML file(s) within Amazon S3, set the URI property to the URI of the Bucket and Folder where the intended XML files exist. In addition, at least set these properties:
To connect to XML file(s) within Box, set the URI property to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect to Box.
To connect to XML file(s) within Dropbox, set the URI proprerty to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect to Dropbox. Either User Account or Service Account can be used to authenticate.
To connect to XML file(s) within SharePoint with SOAP Schema, set the URI proprerty to the URI of the document library that includes the intended XML file. Set User, Password, and StorageBaseURL.
To connect to XML file(s) within SharePoint with REST Schema, set the URI proprerty to the URI of the document library that includes the intended XML file. StorageBaseURL is optional. If not set, the driver will use the root drive. OAuth is used to authenticate.
To connect to XML file(s) within Google Drive, set the URI property to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect and set InitiateOAuth to GETANDREFRESH.
The property is the controlling property over how your data is represented into tables and toggles the following basic configurations.
See the Modeling XML Data chapter for more information on configuring the relational representation. You will also find the sample data used in the following examples. The data includes entries for people, the cars they own, and various maintenance services performed on those cars.
With a Connection Manager created, you can now pull data from XML or push data into it using SSIS data flow tasks.
Solution: Verify OAuth settings, client IDs, secrets, or token permissions for your XML. Contact [email protected] for OAuth troubleshooting.
Solution: Check firewall, proxy, and VPN configurations. Contact [email protected] for specific port requirements.
Solution: Confirm you selected the correct schema or database when querying XML.
Now that you have installed, licensed, and configured the SSIS Components, here are scenarios you can use to explore our SSIS tools:
| SSIS Component | Article Title |
|---|---|
| BIML | Use Biml to Build SSIS Tasks to Replicate XML to SQL Server |
| SSIS Export | Export Data from SQL Server to XML through SSIS |
| SSIS Import | Import XML Data into SQL Server using SSIS |
| SSIS Lookup | Insert New or Update Existing XML Records from SQL Server |
If you need assistance at any point:
Be prepared to securely upload the log file upon request when reaching out to [email protected] for troubleshooting analysis.
For questions not covered in this FAQ, contact [email protected].
Download a free trial of the XML SSIS Component to get started:
Download NowLearn more:
π XML Documents IconPowerful SSIS Source & Destination Components that allow you to easily connect SQL Server with XML data stores through SSIS Workflows.
Use the XML Data Flow Components to synchronize with XML documents. Perfect for data synchronization, local back-ups, workflow automation, and more!