XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1182)
- Stylus Studio Technical Forum (14569)
-> + EDIFACT guideline from Stylus ... (3)
-> + CSV file putting all the data ... (5)
-> + Can't install Home version 64b... (5)
-> + presale - Can I covers this sc... (5)
-> + Problem with UNB (5)
-> + Splitting EDIFACT files pipeli... (4)
-> + Problem with SAXO processor - ... (5)
-> + PDF Format Help (4)
-> + License check unreliable (2)
-> - XML related issue (1)
-> + Need help regarding pipeline o... (2)
-> + Error converting XML to EDIFAC... (4)
-> + XSLT Profiling for XSLT 1.0 s... (2)
-> + Grouping (2)
-> + Best Practice for Pipeline err... (2)
-> + pdf generation (4)
-> + Problems excuting a Pipeline w... (2)
-> + XML serializer (3)
-> + Supported EDIFACT versions (5)
-> - Anyone know XActimate ESX file... (1)
-- [1-20] [21-40] [41-60] Next
+ Website Feedback (247)
+ XSLT Help and Discussion (7617)
+ XQuery Help and Discussion (1966)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Rob OaksSubject: Optimal for DB to XML?
Author: Rob Oaks
Date: 08 Aug 2014 03:04 PM
I am trying to determine whether Stylus Studio is an optimal solution for the following scenario:

1. Source is a SQL Server database containing insurance policy information. Database schema is predetermined and includes perhaps a dozen tables with various one-to-many, and many-to-many relationships.
2. The top of the database hierarchy is the policy number. Given a policy number, it is possible to write a set of queries that extracts all the data that pertains to that policy. This includes a record in the Policy table (contains basic insured information), all of the records in the Risk table (represents autos, houses, etc. covered by the policy) that are related to the Policy record, and all of the records in the Coverage table (represents coverages for each Risk record) that are related to each Risk record.
3. The bottom line goal is to create a black box that, given a policy number, extracts the relevant data from the database and create a hierarchical XML representation of that policy.

1. Preferably I would like to auto-generate an XML schema (XSD) from the database and use this XSD as the target of the extraction.
2. No transformations will be performed on the data and I am not too concerned about the quality of the XSD that is generated because I’m only doing this as a way to “re-source” the data for transmission (see the next point).
3. All I care about is transforming the data for the specified policy to an XML string with no loss of information. I will then be transmitting that string via Web Service to a server that will place it in a message queue, where the transformations and detailed processing (I will use XQuery to extract and transform the data) will occur. The resulting XML will typically be less than 200K, though the source database could be many Gb.
4. I need to be able to turn the MapForce code into Java source, so that I can ultimately create a JAR that I can deploy on a server somewhere.

Remember: I already have an ETL platform/process; I just need a way to transform a set of hierarchical database records to XML for wire transfer.

Is Stylus Studio a good solution for this scenario? Can you outline the steps that would be required in Stylus Studio?

Thanks so much!

Ivan PedruzziSubject: Optimal for DB to XML?
Author: Ivan Pedruzzi
Date: 08 Aug 2014 04:38 PM
Hi Rob,

Stylus Studio XQuery editor provides a rich experience for database to XML extraction.

Depending on how complex is your database schema you may find possible to use the mapping UI. Here a video tutorial which shows the basic

For licensing related question I will contact you off list.

Ivan Pedruzzi
Stylus Studio Team

Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.