Date: Mon, 5 Mar 2012 21:13:50 +0000
Reply-To: "DUELL, BOB" <bd9439@ATT.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "DUELL, BOB" <bd9439@ATT.COM>
Subject: Re: Getting at teradata: ODBC or OLEDB?
Content-Type: text/plain; charset="us-ascii"
I don't think it's obscure at all; it's a good question!
I assume you are talking about SAS on Windows (since I don't think OLE DB is available on UNIX). So, since you have both SAS products licensed and you have (or can get) both Teradata clients and since the only reason you would pick one over the other: why not perform some tests? Just configure both connections then measure how long it takes to create a new test table and how long it takes to copy them back from Teradata into a new SAS dataset.
Make your test table fairly complex (a handful of variables with different data types) and make its size representative of the files you might work with (perhaps a couple hundred thousand rows). As a tip, define the SAS variable you want to use as the table index as the first one in your dataset (but there may be an ODBC or OLE DB option you can use.
I'd be curious of the results. If you decide to do some testing, please post your results. For that matter, I might find time to test it myself. I use SAS/Access to Teradata daily but only on UNIX. I also use some software called "Teradata SQL Assistant" on my PC (available from your local Teradata person, probably the same one who gave you the drivers). However, I will point out that the new version of SQL Assistant can connect to Teradata using either ODBC or .NET. The .NET connections are MUCH faster than ODBC, but that could be the tool itself rather that the highway.
I'm a big fan of both SAS and Teradata and really like the SAS/Access product. If you will be using Teradata extensively, I'd suggest asking for a license. Again, I cannot speak toward the performance on Windows, but it's stellar software on UNIX.
From: SAS(r) Discussion [mailto:SAS-L@listserv.uga.edu] On Behalf Of Pardee, Roy
Sent: Monday, March 05, 2012 11:29 AM
Subject: Getting at teradata: ODBC or OLEDB?
This is obscure, but I figure someone may have looked at this at some point.
I'm going to be moving data in & (mostly) out of a teradata db server with SAS. We have SAS/ACCESS for ODBC and OLEDB licensed (but *not* the native TD SAS/ACCESS module). I've got the ODBC driver installed & can connect that way, but I see that TD offers an OLEDB provider as well. Is there any reason to favor OLEDB over ODBC for connections from SAS?
Roy Pardee | DATA WRANGLER
Group Health Research Institute
PHONE 360-447-8773 | 206-287-2078
GHC Confidentiality Statement
This message and any attached files might contain confidential information protected by federal and state law. The information is intended only for the use of the individual(s) or entities originally named as addressees. The improper disclosure of such information may be subject to civil or criminal penalties. If this message reached you in error, please contact the sender and destroy this message. Disclosing, copying, forwarding, or distributing the information by unauthorized individuals or entities is strictly prohibited by law.