Archives of the TeradataForum
Message Posted: Mon, 28 Jan 2002 @ 22:16:37 GMT
Several of you voiced questions or reservations concerning SAS interaction with the Teradata DBMS. If you have not read it, please look up "SAS/ACCESS Interface to Teradata White Paper" on the web. This will answer many questions, and also point out the many engineering man hours SAS devotes to properly interfacing to Teradata.
If SAS takes a long time to pull data off the system for analysis, this probably means a large result set for the SQL submitted to Teradata, or perhaps (but a bit less likely) complex SQL that has substantial execution time on the Teradata server. Either way, SAS has tools to show the SQL and to help isolate where time is spent. In addition, you can use BTEQ independent of SAS to submit the identical SQL and see where time is spent. SAS/ACCESS to Teradata will have integrated FastExporting in the next version to expedite large data transfers.
As to inserts skewing the access log, this bug is on our list to be fixed. In the meantime, the SAS product has integrated FastLoading, which as a workaround (and an infinitely faster insertion method) eliminates this problem.
As to investigating problem reports, problems first are diagnosed by SAS's easily reached technical support staff. As with any such staff, staff members can be overzealous in attempting to resolve a problem without asking for help from development. If you feel a problem has gone unresolved for too long, feel free to email me and I will look into it and get back to you.
Thanks for your feedback,
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|