<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://paulvero.ulitzer.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Paul Vero</title>
 <link>http://paulvero.ulitzer.com/</link>
 <description>Latest News from Paul Vero</description>
 <language>en</language>
 <copyright>Copyright 2012 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Thu, 17 May 2012 21:12:30 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>The Incredible Bulk</title>
 <link>http://paulvero.ulitzer.com/node/1901792</link>
 <description>The ability to load data on the ASE quickly is achieved with the bcp utility. Customer demand called for bulk load capabilities with other database APIs such as JDBC and ODBC. In JDBC, the executeBatch() command provided batching insert commands to load data in large amounts, not taking advantage of the ASE bulk capability. The ASE JDBC driver, jConnect, and the ASE ODBC driver contain enhancements to utilize this ability. I’ll cover the concepts on how the API calls handle this and also sneak a look behind the scenes at the TDS level. The end result demonstrates more options for developers to use their API of choice. 
This article will present the concept in terms of the API calls describing what they mean, and walking through a simple example. Also, for those interested in the mechanics, the communication between the client and server will be discussed from a trace level standpoint. It’s important to see the distinction between just batching commands and bulking them up as a stream of data. &lt;p&gt;&lt;a href=&quot;http://paulvero.ulitzer.com/node/1901792&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 11 Jul 2011 06:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://paulvero.ulitzer.com/node/1901792</guid>
 <comments>http://paulvero.ulitzer.com/node/1901792#feedback</comments>
</item>
</channel>
</rss>

