In my last blog I briefly touched upon storing XML documents in MSSQL. Now let’s discuss creating them instead. Specifically I mean creating them using the FOR XML keywords in MSSQL. While this functionality exists in other database systems such as Oracle and DB2, their implementation is different and warrants a separate blog post.
Most of us are familiar with selecting data using a SQL command and retrieving some sort of result set. With XML being used so frequently for a wide range of applications, it is not uncommon for a programmer to want to build an XML message out of data stored in a database somewhere. Instead of using SQL queries and looping over result sets, it is possible in MSSQL to use the FOR XML declaration to actually return that data as pre-formatted XML. Continue reading
Data Integration is defined as, “the combining of fragmented data residing in different sources and locations which are aligned to support business goals”. There are many reasons to bring data of different types (flat file, DB2, or even spreadsheets), possibly residing on different servers, to one main location to be integrated together. If you do Electronic Data Interchange (EDI), translating data between an EDI fixed format and application variable format files, then you have already been doing a piece of the data integration puzzle. Continue reading
Camels can be stubborn and angry animals if you don’t take care of them. Lucky for you the EXTOL development team has figured out how to tame them. And we even taught them how to work with data!
Everywhere we look today we can see patterns. They’re in your shirt or tie. You witness traffic patterns (big or small) on your way to work. There are even patterns of integration – Enterprise Integration Patterns (EIP). These patterns allow you to define standard ways of dealing with messaging systems. Examples of these patterns include content-based routing and wiretapping. Continue reading
In my previous blog post I talked about the SQL standard. It is tempting to visualize a standard as a list of rules nailed to a wall. However things in this industry have a habit of becoming a moving target. Continue reading
Successful EDI implementations must begin with the development and employment of efficient object naming conventions using “best practices”. This will avoid aggravation and redevelopment at a later time. “Doing it correctly the first time” is a most-relevant piece of advice. This is of particular advantage when creating files (tables) to store EDI data (the implementation and deployment of EDI interface / staging files and in support of both inbound and outbound EDI transactions).