pureQuery and .NET - Yes you can (get better performance)
IBM_Optim 27000269HS Visits (3365)
As you may recall, when we announced Data Studio pureQuery Runtime 2.1 for LUW, one of the new features in the release was ability to use pureQuery with .NET applications. This support is available for all of the DB2 servers; however, I want to focus a bit on this from a z/OS perspective, since it is primarily these customers who let us know that they heard and liked the pureQuery for Java story we were telling, but that they needed something like this for .NET as well. They wanted the advantages of static SQL - for security, manageability, and performance reasons.
So we did add that support for .NET in the 2.1 release of the Data Studio pureQuery Runtime and in the latest IBM ADO .NET provider. Although it doesn't have all the rich tools support that Java does, it provides many of the key benefits that Java shops can get - static SQL performance and consistency, static SQL authorization model, and the ability to create uniquely named packages that can help DBAs and system programmers isolate performance problems to a particular application and particular SQL statements. And, since it's using client optimization, that means your applications can get these benefits without having to change source code.
To validate the performance benefit, I'm very happy to announce that we've published the results of our performance study (using the IRWW benchmark) of the pureQuery support for .NET. I don't want to spoil the surprise, but the numbers are very impressive with huge increases in throughput and dramatic reductions in CPU per transaction.
Also, be sure to see this developerWorks tutorial. It's a good step-by-step guide to the process of enabling .NET applications to use pureQuery.