About kiranv_

kiranv_ · ‎08-23-2017

looks like TPT is not compatible with proc ds2. Some one from SAS could tell us more about this . I think you can try just fastload = yes dataset option.

kiranv_ · ‎08-22-2017

first of all I think you should have dbcreate_table_opts= 'primary index(columnof index)'); in your dataset options otherwise you may get skewed table in Teradata if your first column is not unique. I feel there could be many reasons for the this, first of all workload at that particular point in time and also this run times are so small, if you run the same thing multiple times you may have slightly different times. previusly i tried to bench mark before by running same query after few minutes, often yielding slightly different results, this can attributed to workload at that point of time. if you really want to benchmark you need to run the tables with lot of data, keeping everything else constant. One more reasons is fastload works by opening multiple sessions, there are limited amount of sessions per utility which can be pretty much used by other users and you have to wait for your turn.

kiranv_ · ‎08-22-2017

this is very interesting. I have not used proc DS2. can you do try tpt in libname statemnt as something shown below. libname tera teradata user=testuser pw=testpw TPT=YES;

kiranv_ · ‎08-22-2017

As far as I know sas dataset can be read concurently. Please checkout interesting link below http://support.sas.com/resources/papers/proceedings15/3380-2015.pdf

kiranv_ · ‎08-22-2017

please check this below link http://support.sas.com/kb/41/925.html

kiranv_ · ‎08-22-2017

this is an encoding issue. Encoding setting in sas config might defaulted to latin1. we had problem like this before and we tried to fix it with changing a session option, it did not worked out. What we were suggested at that point of time to change the encoding setting to UTF8 in sas config file. do a proc options option=encoding; run; I think you will see latin1 as your encoding. There might be another solution, but I am just sharing my experience.

kiranv_ · ‎08-20-2017

I am not very sure, But I guess, this is an encoding issue. Encoding setting in sas confiuration defaulted to latin. Whenever you have something in oracle datset which is not latin you might be seeing this error. do a proc options option=encoding; run; see whether it is latin1 on your location look into this article http://blogs.sas.com/content/sgf/2014/09/26/encoding-helping-sas-speak-your-language/ If possible check data defintion language(DDL) of your oracle table. Check whether it is unicode. There are numerious ways to find whether you non-latin data in your oracle dataset.

kiranv_ · ‎08-17-2017

@Haikuo and @Ksharp solutions in below link perfect for this scenario https://communities.sas.com/t5/Base-SAS-Programming/Concatenate-multiple-rows-into-a-single-value/td-p/132882?nobounce

kiranv_ · ‎08-15-2017

somthing like this should work data have; input UNIT $ Amount; datalines; $ -162 $ -398 $ 160 ; proc sql; select case when amount lt 0 then '-'||strip(unit)||strip(put(abs(amount),5.)) else strip(unit)||strip(put(amount,5.)) end as newcol from have;

kiranv_ · ‎08-15-2017

@AndrewHowell thank you, that was good paper. Do you know what type of queries that are generally not passed to DBMS. Just looking for some benchmarking. Does any of datastep constructs that are passed to DBMS.

kiranv_ · ‎08-15-2017

Thank you so much @Reeza. Do you know whether regular expressions are passed or not.

kiranv_ · ‎08-14-2017

Hi, I am trying to understand, when implicit sql pass through for Teradata is used, what type of queries or SAS/functions that are not passed to Teradata(queries with remerging statistics are not passed to teradata). I have read paper by Howard Plemmons https://www.mwsug.org/proceedings/2015/BB/MWSUG-2015-BB-03.pdf and paper by Fred Levine http://www2.sas.com/proceedings/sugi26/p110-26.pdf and also paper by @JBailey http://www.scsug.org/wp-content/uploads/2013/11/The-SQL-Tuning-Checklist-Jeff-Bailey-SAS.pdf and also looked into SAS/Access for relation databases http://support.sas.com/documentation/cdl/en/acreldb/69580/PDF/default/acreldb.pdf All this articles inform me that distinct, upcase and joins are usually passed to Teradata to name a few. This list of queries sent to teradata is too small. I also know that by using options sastrace=',,,d' nostsuffix, we can find whether a query has been passed to teradata or not. I would like to know whether there is comprehensive list that tells us which string or numeric function that are not passsed to teradata. Does regular expressions in SAS are passed to teradata. Is this information available anywhere or is it we need to try out each scenario.(I also understand that there are lot of SAS statistical functions that cannot be mapped to Teradata). Please let me know your expert opinions. Thanks

kiranv_ · ‎08-10-2017

what you are saying indicates that it is getting assigned to default length that is $1024. I guess thhis is probably configuration level settings, which is overwriting your libname options, datset options. if possible, please contact your sas admin and discuss about his. I am very curious to know outcome of this.

kiranv_ · ‎08-10-2017

we faced similar issue one year ago, where one of the query was taking long and often they were connection time out. This has to do with Oracle settings, where in connections settings has to changed at oracle side. Oracle team refused to change the settings and We finally optimized our query to circumvent the issue.

kiranv_ · ‎08-10-2017

have this options options sastrace=",,,d" sastraceloc=saslog no$stsuffix; and try this proc sql; insert into xxx.test1 (DBMAX_TEXT=8000) select * from work.test; quit;

Online Status	Offline
Date Last Visited	‎10-24-2024 11:47 PM

Re: 2023 Customer Awards: ICON - Curious Thinker

Re: Macro code to iterate through list

Re: Creation of SAS library via macro variable

Re: removing the special code value

Re: Regular expression: Negative Lookahead

no overwriting of results in result window of SAS EG

Re: Floating Point Zero Divide

Re: SQL to Proc SQL

Re: ERROR: Result of WHEN clause 2 is not the same data type as the pr...

Manipulating Data in Base SAS® Part 4 – Lookup

Re: How do i list all libraries and libref in SASApp

2024 Customer Awards: Holland Numerics Ltd - Curious Thinker

Using PROC DQSCHEME Part 1: Utilizing the CREATE statement

3rd Place Winner - 2023 Customer Awards: ICON - Curious Thinker

Re: Column not Accepted when Creating Oracle Table from SAS Dataset

Re: Macro code to iterate through list

Re: Creation of SAS library via macro variable

Re: How to convert date character type to numeric?

Re: Monotonic function with group by proc sql

Re: how to use TPT in DS2 data step?

Re: question about writting SAS data back to Teradata, why using TPT n...

Re: how to use TPT in DS2 data step?

Re: SAS data set running queue

Re: Transcoding problem

Re: Transcoding problem

Re: sas etl

Re: Concatenating a column based on another column

Re: -$160 instead of $-160

Re: Implicit pass through--which queries are send/not send to Teradata

Re: Implicit pass through--which queries are send/not send to Teradata

Implicit pass through--which queries are send/not send to Teradata

Re: Insert long text variable from SAS into Oracle database table

Re: SAS/Access Oracle timeout

Re: Insert long text variable from SAS into Oracle database table

SAS Inner Circle Panel

SAS Analytics Explorers