For SaaS providers today, performance is perhaps the most important business metric.

Why? Because it directly impacts both top and bottom lines.

When SaaS performance declines:

• Support costs increase—as technical support is overburdened by incidents
• SLAs are missed—leading to brand damage and, in some cases, penalties
• Operating costs increase—as providers add more infrastructure to compensate
• Customer loyalty and renewals decline—as the app fails to deliver for users

Some SaaS providers now recognize that the data access layer is a critical performance pathway that has the potential to dramatically impact application responsiveness and cost efficiency.

On Thursday, May 17, Progress | DataDirect will host a complementary webinar to discuss why and how performance and dollars are lost to inefficient data access. And how you can do better.

Register now for “SaaS at the Speed of Business: App Performance on Overdrive.”

You’ll learn the “New Rules” for SaaS performance and why “good enough” is no longer good enough, particularly for vendors targeting the Fortune 1000. Here, expectations are for zero-latency responsiveness. SaaS providers with enterprise ambitions must be prepared to deliver!

Database drivers are often dismissed as commodities, mature technologies that are more or less the same. I believe this is superficial view of a technology whose purpose is anything but.

Look around and you’ll see plenty of useful analogies for the database driver.

It’s the narrow pipe in a plumbing system that slows (or, as we’ll discuss, has the potential to accelerate) throughput. It’s the narrow neck of a bottle that constrains the flow of liquid.

My favorite analogy is found in consumer electronics. Your high-fidelity surround sound system performs no better than the cables and connectors that bind its componentry.

Neither does your SaaS app.

Just like upgrading the commodity cables that ship with your surround sound system, you’ll often see dramatic performance improvements in your SaaS app simply by swapping out the drivers.

Let’s take a quick look at the numbers.

On the same hardware, relative to commodity drivers, Progress | DataDirect has measured:

• Nearly 4X the transaction volume
• More than 5X the data throughput
• Twice the processing speed

What does this mean?

It means that the performance potential of your SaaS app is often lost in the data access layer.

It also means that, to achieve application performance, there’s a good chance you’re unnecessarily throwing physical, virtual or cloud infrastructure at the problem.

Register now for “SaaS at the Speed of Business: App Performance on Overdrive” and we’ll show you how to make your SaaS app perform, while saving you real money along the way.

I look forward to seeing you online on Thursday, May 17th!

Are you looking to improve performance of JDBC batch inserts into SQL Server, Oracle, and Sybase?   If so, you are not alone based on the buzz surrounding codeless DataDirect Bulk Load in our Type 5 Progress DataDirect JDBC drivers.  The common requirement is to speed up inserts for large amounts of data from Java Application environments; and shops are pleasantly blown away at how easy it is to speed things up in a single step with no code changes required.

Before DataDirect Bulk Load, organizations were considering various approaches they considered less than desirable for their project. I’ve heard plans to redevelop the application to generate an intermediate CSV file and call external bulk load utilities after porting it from Linux to Windows. Another shop was even considering a Java to .NET layer to perform the insert.

How do you enable codeless DataDirect Bulk Load for your JDBC batch insert in a single step?

1. Add two options to your connection string:

;EnableBulkLoad=true;BulkLoadBatchSize=n (where n is an integer representing the JDBC batch size)

By the time you finish reading this sentence, you could have made the change yourself and be ready to start a batch to bulk insert!  This is one of the most innovative features I’ve seen in a JDBC driver as it translates the batch inserts into the database’s native bulk load protocol transparent to the application.

What about streaming result sets or consuming CSV files?

An additional feature of DataDirect Bulk Load is the DDBulkLoad extension.  You can use it to bulk load or export CSV files to/from any DataDirect driver that supports DataDirect Bulk Load.  Additionally, the drivers can be used to stream JDBC result sets from one data source to another.

Bulk Load from JDBC ResultSet rs:

Bulk Load from CSV file:

For complete details, please see the chapter on Using DataDirect Bulk Load in our User’s guide.

Do you have any batch code samples for a POC to test performance between EnableBulkLoad=true|false?

Try the JDBC batch sample below to simulate batch to bulk insert performance and modify the column bindings for your table.

How can the database be tuned to improve bulk load performance?

SQL Server
1. Verify the Database’s recovery mode per msdn article on Considerations for Switching from the Full or Bulk-Logged Recovery Model. To verify the recovery mode, the database user can run the following query:

SELECT name, recovery_model_desc
FROM sys.databases
WHERE name = ‘database_name’ ;

Note the recovery_model_desc returned by this query (expect to return,’BULK_LOGGED’).

2. Check the Prerequisites for Minimal Logging in Bulk Import.

Sybase
For Sybase, some additional database configuration is required when the destination table for a bulk load operation does not have an index defined. If you are using a destination table that does not have an index defined, you can ask the database operator to execute the following commands:
use master
sp_dboption test, “select into/bulkcopy/pllsort”, true

This option is required to perform operations that do not keep a complete record of the transaction in the log. For more information, refer to the Sybase documentation.
Alternatively, you can define an index on the destination table.
Failure to properly configure the database results in errors such as the following: “You cannot run the non-logged version of bulk copy in this database. Please check with the DBO.”

Oracle
DataDirect bulk load is supported on versions 9.0.1 and higher.

Who do these guys think they are?

You might be wondering, how does Progress DataDirect always seem to add ground breaking functionality to their JDBC drivers?

To get an idea, I googled the question and found that 3 of my DataDirect colleagues are JDBC Experts with offices down the hall from mine (Mark Biamonte, John Goodson, and Jesse Davis) working on the JDBC 4.1 specification.  Therefore, you should expect innovation and superior data connectivity from DataDirect; and can get started today with a 15 day trial:

1 . Install Progress DataDirect Connect for JDBC using the instructions in the Progress DataDirect Connect for JDBC Installation Guide.  You can download a free, 15-day trial of the Progress DataDirect SQL Server JDBC driver (including DB2, Oracle, Sybase, MySQL and Salesforce).

2. Or call 1-888-876-3101 to speak with a live Solutions Consultant to learn more about DataDirect JDBC bulk load.

It seems that everyone in IT is talking about security these days.  And it’s hardly surprising, given the recent security breach with VISA and mastercard, everyone in AND out of IT is wary of identity theft and its consequences.

I came across a New York Times article from last summer, that focused on why user credentials should be encrypted, and why you should be losing sleep at night if they are unencrypted.   What’s interesting is that given the multiple breaches in data security we have seen in recent years, some folks still prefer to roll the dice and chance it.  And in some cases, they might be chancing it with customer information!

For example, some ODBC drivers to SQL Server do not encrypt user credentials – or they might have a weaker encryption of passwords and absolutely no protection for the user ID.  The New York Times article cites a well-known electronics company that suffered a breach, where their data, including user credentials, was stored and being transmitted in plain text.  A hacker’s dream (and an IT director’s nightmare)!

DataDirect ODBC Drivers encrypt user id and password information – regardless of which SQL Server authentication method is used.  For additional data protection, DataDirect Connect for ODBC drivers use SSL encryption to encrypt all of the data across the network.  Internet Security Advisors’ Group concurs in their evaluation of Progress DataDirect security features:

“Based on our independent assessment, we believe that using Progress DataDirect Connect for database access is one of the best proactive security measures an organization can take to reduce security related losses.”

Whether your data is in the cloud (Salesforce.com, database.com, force.com), in a data warehouse (Sybase IQ, Greenplum, Teradata), or in a traditional relational database such as Oracle, DB2, or SQL Server, don’t roll the dice on your security strategy, or your company’s reputation.  Download DataDirect Connect for ODBC Drivers and ensure best-in-class security for your critical data.

We are really excited about the response from Oracle shops to our SQL approach via ODBC and JDBC to fully integrate Oracle applications with Salesforce.com at Collaborate 12, Oracle User’s Community.  There was a roaring applause and folks tweeted about our session (#940 – SQL Access to Salesforce.com Data) that included a demo of a SQL-92 inner join query against Salesforce.com in real time from Oracle SQL Developer.

Sandy Estrada ‏ @MsSandyE

Learned how to easily integrate #Salesforce with #OBIEE leveraging@datadirect_news , will recommend to my clients. #C12LV

Anju Rao ‏ @anjugrao

Great presentation from @datadirect_news on SQL and #salesforceconnectivity to both SaaS and OnPremise BI Tools. #C12LV #Oracle#EPM

Cloud Conversion ‏ @cloudconversion

Interesting session by @datadirect_news at #c12lv

Qingchen Chen ‏ @rmoug

Nice talk to Sumit at data direct booth #clv12 #c12lv

If you were unable to visit Progress DataDirect at the Collaborate 12 Oracle User’s Conference, here are the top 5 questions we heard from Oracle shops on leveraging SQL access to Salesforce.com from various applications including: OBIEE, E-business Suite (EBS), JD Edwards, Oracle Warehouse Builder or Data Integrator, PL/SQL and Application Development Framework (ADF).

1. How do you model the RPD in OBIEE directly against Salesforce.com without a staging database?

With a direct ODBC connection from OBIEE to Salesforce.com, you have the option to model your metadata directly against Salesforce.com.  You can read more about our experiences with OBIEE integration with Salesforce.  And an OBIEE consultant with over 30 years experience stopped by to share that the mappings will be generated automatically in newer versions using the foreign keys exposed by the driver!

2. What are my integration options from Oracle E-business suite?

If you’re fetching and inserting data from calls initiated within EBS against Salesforce.com, we recommend creating a Database Gateway for ODBC to Salesforce.  This is the same approach used by Oracle shops for years to integrate with SQL Server, DB2 and Sybase.

And the same ODBC driver can be used with JD Edwards shops running SQL Server.

3. For Oracle Warehouse Builder and Oracle Data Integrator, how does the driver handle transactions against Salesforce for inserts, updates, deletes, upserts?

Since Salesforce.com does not support transactions, we included an option to ignore transactions in the driver so that the workflow can run.  The driver was designed for accessing SAAS data the cloud with built-in fault tolerance to prevent failures.

4. What solution do you have for application development using Oracle’s Application Development Framework (ADF) that requires access to data in Salesforce.com?

We recommend running the DataDirect Connect XE for JDBC Salesforce driver for a direct connection to Salesforce.com.  This enables rapid development of a variety of ADF applications accessing SFDC.

5. Does your driver support the rest of the Salesforce platform?

Yes, we support connectivity to force.com applications and database.com.

To summarize the excitement at the conference, an architect waiting in line for Starbucks shared that he is underway with a custom development project with a consulting firm to integrate EBS with Salesforce.com; and he then asked how Progress DataDirect does it.  I shared we have out-of-box integration with ODBC and JDBC available.  He then smiled real big and replied “oh my gosh”.

Need to integrate your Oracle Shop with Salesforce?

1. Download free 15 day trial of the DataDirect Connect XE for ODBC or JDBC Salesforce drivers to integrate an unlimited number of BI applications with Salesforce.

2. Or call 1-888-876-3101 to speak with a live Solutions Consultant to learn how other organizations are making progress with DataDirect Connect Salesforce SQL access.

Join us in Las Vegas for COLLABORATE 12 – described as the “…one event that delivers the full spectrum of Oracle Technology and Applications education that you need to boost results and drive efficiency all year long…”. In addition to showcasing our products at booth 1618, we will demonstrate how to improve application efficiency, as well as enable your Oracle and other ODBC/JDBC applications to have SQL Access to Salesforce.com! 

Join us for our session Monday, April 23 at 11AM, where Sumit Sarkar and I will present a demo of Oracle SQL Developer, in conjunction with Database Gateway for ODBC (DG4ODBC) connecting to Salesforce.com – just as you would connect to SQL Server, DB2, Oracle, or any other relational database, with a SQL application!   This session will be dynamic, with plenty of opportunity for audience participation, two demos, and a whiteboarding session.  Sumit and I also want to hear about your Salesforce integration strategy and your data access challenges – so much that we have gambling chips on offer for participating in the discussion.

With all the next generation technology available today from business intelligence, operational responsiveness and cloud computing; organizations still rely on Microsoft Access.  From what Salesforce shops are telling me, there are very compelling use cases from SMBs to the Fortune 100 for connectivity from MSAccess to Salesforce.com.  And I can relate since I manually run weekly reports using Microsoft Excel to join Salesforce objects without relationships.

Why are organizations using MS Access for integration to Salesforce?

Some of the use cases shared by business analysts include:

• Target customer marketing campaign
• Create invoices from contacts
• Run ad hoc SQL queries

And it’s common that these analysts from finance, marketing and sales have enterprise business intelligence solutions running the very same DataDirect Connect XE for ODBC Salesforce drivers on large multi core servers.  However, these users are just more productive with MS Access since they can get their data without having to engage a hierarchy of business and IT approvals.

Get started with real time Salesforce integration with MS Access 2010 in 15 minutes:

1. Determine whether your MS Access is 32-bit or 64-bit, and download the free 15 day trial of the DataDirect Connect or Connect64 XE for ODBC driver.

2. Go to Start > All Programs > Progress DataDirect Connect and Connect XE for ODBC 7.0 > ODBC Administrator

3. Click on User or System DSN and click ‘Add’

4. Select ‘DataDirect 7.0 Salesforce’

5. Enter Data Source Name as ‘Salesforce’

6. Click on the ‘Advanced’ tab, and enter the following properties in the “Extended Options” field: WorkArounds=16777216;WorkArounds2=8192

7. Click test-connect

8. For user, enter your Salesforce account e-mail address

9. For password, enter the password + security token (if required)

10. Click OK and you should see the “connection succeeded” dialog

11. Launch MS Access 2010

12. Select “Blank Database” template and create access database

13. Click on External Data

14. Click “ODBC Database” Button

15. Select “Link to data source by creating  a linked table”

16. Select Machine Data Source and choose your Salesforce DSN.

17. Select Salesforce tables to link.

18. Click OK and open a table to view the contents.

How to fix common issues with MS Access and Salesforce.com integration:

1. System error 126 or 193 on test connect

This means the jvm.dll in the JRE of matching architecture (32-bit or 64-bit) cannot be loaded from the system path.  Search the knowledgebase for ’126 and salesforce’ for additional articles.

2. error -7711

This error is thrown when a warning or error is coming back from the driver for which the length is too long for MS Access to display.  It is recommended to generate an ODBC trace log to determine the error.  One example is documented here.

3. reserved error (-7748): there is no message for this error

Verify step #6 was followed above.

4. #deleted returned for all fields from import

Verify step #6 was followed above.

5. Error is thrown after selecting data source: [DataDirect][ODBC Salesforce driver][Salesforce]Unable to create local database file: C:\sandbox.config The cause: C:\sandbox.config (Access is denied)  This error often caused by the driver not having write access to the target directory.

Run MSACCESS.EXE “As Administrator”.  The executable is located here by default, “C:\Program Files\Microsoft Office\Office14\MSACCESS.EXE”; and run “As Administrator”.

I am feeling a little threatened now:

Once you’re successful with your project, we encourage you to share with your business intelligence and data warehousing groups how you personally solved Salesforce integration using DataDirect Connect XE for ODBC Salesforce.  As an IT professional, I am feeling a little threatened now that Business Managers are deploying CRMs in the cloud; and Business Analysts are solving the complex integration challenges across the entire organization!

And please share your use case with a blog comment …

The recent breach in credit card security with VISA and MasterCard accounts is just one of many stories we hear on a regular basis that put us on edge when it comes to our personal data getting compromised. Some IT folks in charge of application and database security might say “what we have is good enough”, yet that is exactly what hackers count on when they attempt to steal data and information.

Internet Security Advisors Group (ISAG) recently did a review of data security and how Progress DataDirect can prevent the types of breaches which cost billions of dollars annually.  Supporting NTLM, Kerberos, Database client encryption, and SSL, DataDirect drivers give you the flexibility to build a secure application.  With DataDirect wire-protocol drivers, you can use the best security functionality, across all platforms, with no need for database client libraries (which can invoke a seperate set of security concerns). 

Whether you require ODBC, JDBC, or ADO.NET access to your relational, cloud, or data warehouse data sources, Progress DataDirect provides the necessary options to keep your data secure.

Download Progress DataDirect Drivers today and keep your data secure!

There is a surge in interest for Sybase, Oracle and DB2 ADO.NET providers for use with 64-bit .NET applications built across ADO.NET, Entity Framework, and NHibernate.  Like these shops, you are probably reading this article since you’ve encountered an issue upgrading a development PC or server to 64-bit.

Does Progress DataDirect have 64-bit ADO.NET providers?

Yes, but I get very confused at the question since managed .NET applications run independent of the underlying 32-bit or 64-bit architecture by design.  Then again, not all providers are 100% fully managed code like DataDirect Connect for ADO.NET; and I must be living a sheltered life at DataDirect.

What challenges am I hearing from .NET shops facing with deployment of 64-bit .NET applications?

• Managing complex deployment of 32-bit/64-bit unmanaged database clients for non-DataDirect ADO.NET providers.  IBM and Oracle have different installers for Windows x64 versus x86.
• Oracle shops running the OracleClient provider that has been deprecated find out quickly that it is not supported on 64-bit platforms.
• Deployment headaches in locked down business critical environments.  For example, it requires several teams and man hours to get an assembly registered in the GAC; much less run an installer for a thick database client.  Or shops might deploy desktop images where users have limited access to make system changes of any kind; and upgrades are expensive.
• IBM no longer supports 64-bit ADO.NET connectivity to iSeries prior to version 6.
• Sybase enhanced Adaptive Server ADO.NET Data Provider only supports SSIS 2008, 32-bit.

What are your options with Progress DataDirect Connect for ADO.NET?

• Progress DataDirect Windows Installer (includes silent option)
• ClickOnce
• XCopy (or similar file copy)

For example here is a write-up on the three ways to deploy our Connect for Oracle ADO.NET assemblies to an ASP.NET application.

Everyone is talking about DataDirect’s XCopy style deployment, so how does it work?

For the locked down environments mentioned above, .NET shops are indeed turning to our flexible XCopy style deployment that is independent of machine architectures.  You can follow my “Hello World” Xcopy style deployment tutorial below for a quick POC:

• Create new Visual Studio 2010 Project > Visual c# ASP.NET Web Application
• Right click on Solution Name; Add Reference to DDTek.Oracle.dll
• Right click on Solution Name; Add New Item
• Select “C# Class” and create class named “Class1″ with language as c#
• Click on Default.aspx for Designer View
• Drag “Label” from toolbox named Label1

• Code Sample Below for default.aspx.cs:

• Code Sample Below for Class1.cs:

• Build > Build Website and then Publish
• Select target build location in folder named “myWebSite_source”.
• Copy DDTek.Oracle.dll assembly and DDTek.lic license file to “myWebSite_source\bin”
• Note: For projects building an assembly, you can embed the license file as a resource instead of setting the License Path connection property. See Connect for ADO.NET User’s Guide for further details
• Create New Folder “myWebSite” with web app in c:\inetpub\wwwroot
• Copy (or XCopy) Published Website files from “myWebSite_source” to “myWebSite”
• Launch IIS Administrator, inetmgr
• Navigate to Default Web Site
• Right Click myWebSite and click “Add Application”
• Enter Alias and Physical Path and Test Settings before clicking OK
• Copy files from “mywebsite_source” on build machine to “myWebSite” on web server
• Navigate to site through web browser: http://machine/myWebSite/default.aspx

Summary of Tutorial:

The purpose of the xcopy style tutorial was to demonstrate that deployment using fully managed Connect for ADO.NET providers only required two files (ADO.NET assembly and license file) be copied over to the web server from 32-bit/64-bit development environment to a 32-bit/64-bit application server.   Absolutely no installation to the GAC, registry changes, or database client install were required!   Here is a link to Microsoft’s tutorial for further reference.  Note: additional deployment steps may apply for kerberos authentication, bulk load, or distributed transactions.

Try it out today:

Download and install a free 15-day trial today of the Progress DataDirect Connect for ADO.NET providers.  In addition to easy deployment on 64-bit systems, there are usually at least a dozen other reasons to run your .NET shop on DataDirect; and you can call a solutions consultant today to learn more: N. America: (800)876-3101 | World: +44 (0) 1-344-386-367.

Recently, a Microsoft blogger gave a “shout out” to Progress DataDirect Connect for ADO.NET providers – for DB2, Sybase, Oracle, and SQL Server working with LightSwitch RTM version 1. Not surprising since our resident ADO.NET expert, Sumit Sarkar, wrote a blog about LightSwitch earlier this year with step by step instructions on using DataDirect ADO.NET providers with Microsoft LightSwitch.  Check out what folks are saying about using ADO.NET EF providers with LightSwitch!

Imagine getting prescribed the wrong medication, or being given the wrong diagnosis at the hospital.  That’s what can happen when critical applications and databases go down in a major hospital.  And whether it’s incorrect diagnosis or medication, either one of those scenarios can be deadly.  That’s why UZ Leuven, Belgium’s largest university hospital, chose to work with Progress DataDirect, the world leader in data connectivity, for its migration from Sybase to DB2.

UZ Leuven needed to migrate over 200 critical medical applications from Sybase to DB2.  They could not migrate this many applications at the client level, so the DataDirect OpenAccess solution, where migration could be done at the server level, became the perfect – and only – solution.  Simply deploy the OpenAccess clients to each of the application servers, and connect them to the OpenAccess Server, which can be set to point to Sybase, and then later DB2.

The applications in question could not be down for the several days that would have been required by just switching out drivers.  As Reinoud Reynders pointed out, “The pressure on IT is much higher than 20 years ago, of course, because now when computer systems are down, the hospital has to close, more or less”.  OpenAccess enables the “big bang”, as they call the migration, to be done in one hour instead of multiple days – simply switching from Sybase to DB2 on the OpenAccess Server – to which the clients were already connected.    Read more in our UZ Leuven case study!

With the release of the newest set of Type 5 JDBC drivers, not only do you eliminate the need for database client libraries, but Progress DataDirect Connect for JDBC 5.0 also enhances java applications by offering users additional features without having to add application code.

Do you need application failover but have no access to the application code set?  No problem!  Just set a few connection options in the Connect for JDBC driver to add an application failover feature. 

Do you have a need to quickly and efficiently bulk load data from one data source to another?  Again, no need to change the application code – just take 30 seconds to change the value of a connection option in the driver.  Our bulk enhancement ensures you can bulk from any file delimiter – and you won’t have to learn a new proprietary tool to get the job done.  Perfect solution for dealing with Big Data!

Do you need robust application performance?  OK, so that was a rhetorical question.  No application users ever say “take your time with our critical data, we’ll wait”.  Users of free drivers have described this pain to us multiple times!  One thing that sets Connect for JDBC apart is the ability to consume far fewer resources in the way of memory and CPU cycles – so in addition to turbo-charging throughput, you can save on your hardware by doing much more, with much less.

How many users have said “don’t worry about compromising the security of the data – it’s not that sensitive”?  Not likely.   If you need NTLM authentication from UNIX to SQL Server, you’ve come to the right place!  Just download an evaluation copy of Connect for JDBC!

In addition to the Salesforce.com support we added last year, the new drivers support Database.com and Force.com, we’ve added several new database versions and operating system version support.  Whether you are supporting Oracle, SQL Server, DB2, or MySQL – and many others, enhance your users’ experience with Connect for JDBC.

It must be upgrade season based on number of IBM InfoSphere DataStage shops that I’ve worked with upgrading to the latest 64-bit version.  From reading about newer releases such as version 8.7, this is an exciting upgrade and we’re here to ensure you have complete coverage for 64-bit ODBC data connectivity across Unix/Linux/Windows platforms that are otherwise unavailable.

Why do Infosphere shops choose DataDirect SequeLink 64-bit ODBC drivers for connectivity?

• Per IBM, they provide instructions on installing and configuring the IBM® branded DataDirect® ODBC drivers with InfoSphere® Federation Server Version 9.5 and 9.7.  Since Infosphere DataStage runs on DataDirect, our technology is the best solution for integrating additional 64-bit ODBC data sources that may be unavailable after the upgrade (for example, Progress 8,9 Databases) or for accessing data sources that don’t have bundled drivers in InfoSphere DataStage, such as IBM Lotus Domino or Microsoft Excel.
• The 64-bit SequeLink ODBC Clients are built on the same framework as the branded DataDirect ODBC drivers making them compatible with DataStage and suitable for its high performance parallel framework and enterprise connectivity.
• The 64-bit SequeLink ODBC Clients support the same DataStage platforms running branded DataDirect ODBC drivers across Unix/Linux/Windows.
• IBM recommends this solution to DataStage shops.  For reference, here is an article on how to configure the SequeLink Server Socket to integrate DataStage with MS Excel.
• IBM shops are already familiar with DataDirect SequeLink from use with Cast Iron.

What common sources can be integrated within Infosphere using SequeLink?

• Progress versions 8, 9
• Microsoft Excel and Microsoft Access
• IBM Lotus Notes
• Microsoft Dynamics
• Netsuite.com CRM
• Salesforce.com CRM, Force.com, Database.com
• FileMaker
• Pervasive.SQL (Btrieve)
• dBase, FoxPro, Clipper
• Paradox
• Sybase SQL Anywhere
• Any ODBC 2.x, 3.x driver

So how does DataDirect SequeLink work?

SequeLink is highly scalable, server-based middleware that complements the Infosphere DataStage platform by including complete coverage for 64-bit ODBC data connectivity.  The SequeLink ODBC Socket communicates with any existing 32-bit or 64-bit ODBC 2.x, 3.x driver across Unix/Linux/Windows platforms.  This tier extends support to the 64-bit SequeLink Client for ODBC tier built on the storied DataDirect Connect for ODBC framework on platforms supported by DataStage.  SequeLink supports flexible deployment options allowing both tiers to be installed on the same system, or separately depending on the socket ODBC data source.  For complete details, see our white paper on DataDirect Sequelink.

Who else is using DataDirect SequeLink?

• Home Depot
• Save the Children
• The Winterthur Group
• Northwestern Mutual
• National Center for Genome Research (NCGR)
• Mizuho Bank

Let’s talk about getting 64-bit ODBC connectivity from DataStage running in 15 minutes

Call us today at 1-888-876-3101 to speak live with a Solutions Consultant to learn more about integrating additional data sources into your IBM Infosphere platform.  Or you can download a free trial of the DataDirect SequeLink ODBC Socket today.

Being a solution consultant for the world leader in data connectivity, I have had the opportunity to consult on several database migration projects. I have seen almost every combination of migration to/from SQL Server, Sybase, DB2 and Oracle across Unix/Linux/Windows. Much like Progress DataDirect who is “Switzerland” when it comes to databases, I too love them all from Operational to DWs, on-premise to clouds, SQL to NOSQL … and we’re ready for your next migration.

Why choose Progress DataDirect connectivity for your migration project?

Data connectivity and compatibility with existing applications across different platforms varies greatly between database vendors. DataDirect has been developing interoperable connectivity for decades, and we have the largest standards based data connectivity test suite in the universe across a full range of databases and platforms. We’ve seen everything including issues where one of several result sets get returned, stored procedures fail to return expected data, internationalization and translation issues for character data, etc. Your data migration project cannot afford these kind of setbacks.

And Progress DataDirect bulk load has introduced a brand new set of solutions for database migration.

Here are the 3 most recent projects I have worked:

1. Migrating existing BCP and SQL scripts and custom applications

Problem: An enterprise financial services environment is entertaining a DBMS migration from Sybase to SQL Server 2008, but had thousands of BCP bulk load and ISQL scripts running across Solaris SPARC, Linux and HP-UX. Each of those scripts would have to be migrated one by one to keep the environment running against SQL Server.

Solution: Our exclusive standards based drivers and code samples were used to create database agnostic utilities that can run anywhere against anything. The architect overseeing that project is a popular guy today, and will be a bigger hero when the next database migration project comes along. Learn more by reading an article on BCP and ISQL on Unix/Linux to SQL Server, Sybase, DB2, Oracle.

To complete the transition, it is also important to port existing PowerBuilder for Unix applications from Sybase to SQL Server using the DataDirect Connect for ODBC SQL Server driver.

2. Data Validation

Problem: A consulting group migrated a large amount of data from Sybase to SQL Server 2008 R2 for a prospect. To check for accuracy between source and target, they typically dump data to flat files for comparison on smaller systems. However for larger systems, the size of data becomes unmanageable for such an approach.

Solution: Use data federation to leverage the database server’s processing power and memory to perform a byte by byte comparison to ensure accuracy. Our DataDirect Connect64 for ODBC Sybase driver was the only scalable solution to fetch large amounts of data quickly and accurately for validation from SQL Server Linked Server.

3. Application migration across the enterprise

Problem: Another organization has over 600 systems running various database applications accessing Sybase. They are planning to migrate to DB2 LUW over a 12-18 month period where data may exist in both the old and new systems, and it’s important to ensure the SQL syntax is compatible with DB2. They need an intermediate solution to avoid having to rewrite 60 applications running on 600 systems to support the new DBMS.

Solution: Use the DataDirect OpenAccess SDK to add data access logic at the driver level to achieve data federation between the two systems and modify queries for compatibility with the new DBMS. This makes the migration seamless to users, and no application or script changes are required.

And as I’m wrapping up this post, an Oracle to DB2 LUW 9.7 migration is underway with the help of our DataDirect Connect for ADO.NET providers in an SSRS reporting environment.

Get started today on your project!

1. Download free trial for any DataDirect Database Migration Solution.

2. Or call 1-888-876-3101 to speak with a live Solutions Consultant to learn how other organizations are making progress with DataDirect Connect products for database migrations.

Did you know?

• SAS began as a research project at my Alma Mater, North Carolina State University
• SAS global headquarters in Cary, NC is two exits down the freeway from the Progress DataDirect office.
• Progress DataDirect Connect XE for ODBC Salesforce driver can be used with SAS/Access for ODBC similar to any other relational data source.

Did you say DataDirect has a direct connection to query Salesforce.com and Database.com from ODBC intefaces?

Yes.  We work with customers and prospects every week that run their SAS intelligence on Progress DataDirect drivers through the SAS/Access interface for ODBC.  They are now expanding connectivity to application data sources such as Salesforce.com with the Progress DataDirect Connect64 XE for ODBC Salesforce driver.  There is a good chance this driver is already deployed or being evaluated in your organization today.  Ask around!

Salesforce.com and Database.com will look like native SAS via relational data source

Why choose SAS/Access for ODBC? (from SAS website)

• Integrate more data sources from more platforms.
• Access data directly, easily and securely with native interfaces.
• Gain faster performance and reduce network traffic.
• Support integration through standards, including ODBC, JDBC and OLE DB.
• Support both technical and business users.

Salesforce.com and Database.com will look like native SAS via relational data source

What are SAS shops saying about DataDirect Connect XE ODBC drivers for Salesforce with SAS?

• Easy.  SAS/Access for ODBC to Salesforce does not require an additional data server tier, and only takes 15 minutes to add another connection through SAS/Access for ODBC.
• Intuitive. The XE ODBC driver makes Salesforce.com look and feel like native SAS similar to relational sources: Oracle, DB2, Sybase or SQL Server.
• Consistent. Organizations are already running the Salesforce driver to integrate on-premise applications from Informatica, Oracle, Microsoft, IBM, etc.  Adding SAS connectivity provides a standard interface to Salesforce with a consistent view across the organization of the latest objects exposed through the latest version of the Salesforce.com API.
• Fast: The flexibility of the built in change data capture cache can significantly improve performance over the WAN for extracting data.  In the reverse direction, you can bulk load SAS Data Sets into database.com using the same driver!
• Reliable.  Salesforce drivers are built on the same flagship Progress DataDirect Connect drivers framework that has powered your enterprise data connectivity for two decades across 32-bit and 64-bit Windows, Linux, AIX, Solaris, and HP-UX platforms.

How to get started today?

1. Download free 15 day trial of the DataDirect Connect XE for ODBC driver to integrate SAS/Access for ODBC to Salesforce.

2. Since we made Salesforce.com look and feel like a relational database, follow our tutorial for Superior ODBC Access from SAS on Linux.

3. Or call 1-888-876-3101 to speak with a live Solutions Consultant to learn how other organizations are making progress with DataDirect Connect Salesforce integration.

After working on several POCs last month for integration between Oracle Business Intelligence (OBIEE) and Informatica PowerCenter to Salesforce.com, we have seen a surge in interest for this solution.  Support for ODBC and JDBC connectivity to the Salesforce CRM business application (and database.com) has blown the integration options wide open from OBIEE!  Below is a tutorial on how to create a repository (RPD) to Salesforce.com using ODBC.

Option 1: OBIEE to Salesforce via Data Warehouse

The majority of prospects selecting this option to date are running Informatica, and using our flexible Salesforce CRM integration with Informatica PowerCenter.  For Oracle Warehouse Builder (OWB) integration, Salesforce.com is not a supported business application – SAP R/3, Siebel, PeopleSoft, Oracle E-business.  However, DataDirect Connect XE series ODBC and JDBC drivers provide a fully supported source and target to Salesforce.com as a standard non-Oracle database.  Read my step by step tutorial on setting up the Oracle Database Gateway for Salesforce.

Or choose any third party data integration tool that supports ODBC.

Option 2: Real Time Connection from OBIEE to Salesforce

The option to model and access real time operational data in Salesforce is exclusive to ODBC connectivity using the OBI Admin Tools.  Since Salesforce CRM is a cloud, you can go to town on accessing this operational source for BI through your enterprise SFDC subscription!!  To build a repository, you can perform the following steps:

• Create a New Repository to Salesforce via ODBC DSN

• Select Metadata Types

• Select Metadata Objects

• Yep, that is the physical model for Salesforce.com data!!

• Here is a snowflake schema example built live against Salesforce.com in OBI Admin Tool version 11.1.1.5

Now you can build your star schema directly against Salesforce without the requirement for an intermediate database and ETL job!!

For reference, a general tutorial is available from Oracle on Creating a Repository Using the Oracle BI 11g Administration Tool.

And for real time access to Salesforce from BI Publisher, use the Connect XE for JDBC Salesforce driver. Tutorial on configuring the JDBC driver is available from Oracle.

Option 3: Use both options above with the single point of ODBC integration

Quoted from the ORACLE BUSINESS INTELLIGENCE FOUNDATION SUITE Technical Overview, January 2011

“Combining Transactional Data with Data Warehouse Information: Finally, the Common Enterprise Information Model allows users to combine data from a data warehouse with information from transaction processing systems in a single calculation to get the most up-to-date value of a metric”

How to get started today?

1. Download free 15 day trial of the DataDirect Connect XE for ODBC or JDBC Salesforce drivers to integrate an unlimited number of BI applications with Salesforce.

2. Or call 1-888-876-3101 to speak with a live Solutions Consultant to learn how other organizations are making progress with DataDirect Connect Salesforce integration.