f



Re: MS Access and SAS datasets #9

Howard,

I completely agree on fixing the normalization issue. Oftentimes though it
is something that has to be done later.

SQL Server Express has the .NET CLR built-in which means that you can use
most .NET code in the SQL expression. Regardless of whether this is a
proprietary extension (which it is...a LOT), Access is a less than optimal
database. However, it will probably work as you suggest with some work on
normalizing the structure.

Thanks,
Alan

Savian
"Bridging SAS and Microsoft Technologies"

-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Howard
Schreier <hs AT dc-sug DOT org>
Sent: Tuesday, May 24, 2005 8:48 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: MS Access and SAS datasets

Does SQL Server Express have a lot of proprietary extensions to the SQL
language which provide array processing and the like? If not, the column
capacity may be more a curse than a blessing.

I don't know the specifics of David's project, but based on experience I
suspect that a lot of normalization is possible, and that if it is done,
even the capacity of Access will be far more than adequate.

On Tue, 24 May 2005 20:07:03 -0600, Alan Churchill <SASL001@SAVIAN.NET>
wrote:

>David,
>
>I believe SQL Server Express (which is free) can handle 1024 columns. You
>may want to consider that approach if you have to move it anyway.
>
>Thanks,
>Alan
>
>Savian
>"Bridging SAS and Microsoft Technologies"
>
>-----Original Message-----
>From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of David
>Neal
>Sent: Tuesday, May 24, 2005 6:54 PM
>To: SAS-L@LISTSERV.UGA.EDU
>Subject: Re: MS Access and SAS datasets
>
>You are right, the "slightly" was an understatement on my part.(I guess I
>was being nice.)
>I believe ACCESS is limited to 256 (or 255 I forget which) columns so I am
>required to do a bit of reshaping anyway.  I will be working with
(reshaping)
>the data in SAS and then move it into ACCESS.  I feel much more comfortable
>tweaking it in SAS and then moving it to ACCESS.
>
>David
>
>-----Original Message-----
>From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Howard
>Schreier <hs AT dc-sug DOT org>
>Sent: Tuesday, May 24, 2005 5:26 PM
>To: SAS-L@LISTSERV.UGA.EDU
>Subject: Re: MS Access and SAS datasets
>
>I suspect that you don't need a "slightly" different approach. You probably
>need a significantly different one.
>
>Wide tables are clumsy to work with in SAS, but I think in Access the
>problems will be much more severe. I would think that the occasion of a
>port from one platform to another provides the opportunity to reshape and
>streamline. You will probably find it easier to do this before porting,
>rather than after.
>
>On Tue, 24 May 2005 09:26:21 -0800, David Neal <afdbn@UAA.ALASKA.EDU>
wrote:
>
>>Thanks for the input.  Unfortunately, the datasets are quite wide.  One
>>of them, for example, has over 1000 variables (columns).  Had I been
>>involved with the creation of the initial SAS datasets, I would have
>>suggested a slightly different approach.  Since this wasn't the case,
>>I'm stuck working with things the way they are.  To complicate things,
>>ACCESS won't handle tables that wide so I'm having to mess with he data
>>anyway.  Your (and Howard's) suggestions will at least get me going on
>>the right path.  (Maybe I'll just round up some "slave" labor, AKA a
>>graduate student, to set up all the lookup tables in ACCESS.)
>>
>>Thanks again
>>
>>David Neal
>>
>>Choate, Paul@DDS wrote:
>>> Hi David -
>>>
>>> I agree with Howard that CNTLOUT will give you your formats to develop
>>> lookup tables in Access.   Alternately if your data isn't large and you
>>> don't care about normal form, you could process your variables through
>your
>>> formats with put statements and create parallel formatted data.
>>>
>>> In v9 there's VLABEL, VLABELX, and VARLABEL, etc.  You can use VLABEL
and
>>> array all your _numeric_ and then _character_ columns and create a label
>>> dataset.
>>>
>>> There's also the data dictionary which you can query and use the into:
>>> command to load a macro, or just dump the labels in a dataset.
>>>
>>> Personally, I like to use "options VALIDVARNAME=ANY;" and rename my
>>> variables as their labels before I port data to external databases, but
>I'm
>>> an analyst, not a programmer, and I can hear several mavens groaning in
>the
>>> distance as I write this. ;-)
>>>
>>> Good luck and hth -
>>>
>>> Paul Choate
>>> DDS Data Extraction
>>> (916) 654-2160
>>>
>>>
>>> On Mon, 23 May 2005 14:01:18 -0800, David Neal <afdbn@UAA.ALASKA.EDU>
>wrote:
>>>
>>>
>>>>I'm trying to move several SAS datasets to a single MS Access database.
>>>>When I use proc copy to move the data, I get the following note:
>>>>
>>>>
>>>>
>>>>NOTE: Copying SCFSAS.PT_MISC to SCFFAS.PT_MISC (memtype=DATA).
>>>>
>>>>NOTE: SAS variable labels, formats, and lengths are not written to DBMS
>>>>tables.
>>>>
>>>>
>>>>
>>>>My problem is that I'm interested in keeping the variable labels and the
>>>>formats as well.  Is it possible for SAS to automatically create
>>>
>>> the "lookup
>>>
>>>>tables" from the formats?  Also, is there a way to keep the variable
>labels
>>>>when I move from SAS to Access?
>>>>
>>>>
>>>>
>>>>David Neal
0
SASL001 (990)
5/25/2005 4:00:08 AM
comp.soft-sys.sas 142828 articles. 3 followers. Post Follow

0 Replies
347 Views

Similar Articles

[PageSpeed] 37

Reply:

Similar Artilces:

Re: SAS System Viewer 9.1 unable to open SAS datasets ( SAS 9.1.3)
A question in return: is your table from windows? compressed from another system? and specially with personnel formats hard coded inside? Andre msiddu2000 a �crit : > SAS System Viewer 9.1 was able to open datasets that were created by > V8 engine (SAS 8.2), but is unable to open datasets that are created > with V9 engine (SAS 9.1.3). > > Does this need SAS System Viewer to be upgraded ? > or > Something else needs to be done ? > > -- Andr� WIELKI INED (Institut National d'Etudes D�mographiques) Service Informatique 133 Boulevard Davout 75980 Paris Cedex 20 m�l : wielki@ined.fr t�l : 33 (0) 1 56 06 21 54 ...

Re: SAS
Chandu, You should be able to find some info in the SPD Engine section of the on-line documentation. HTH, Ken -----Original Message----- From: chandu.isi@GMAIL.COM To: SAS-L@LISTSERV.UGA.EDU Sent: Mon, 3 Jul 2006 09:03:00 -0700 Subject: SAS - 9; Partition of SAS Datasets. Hi All, Recently I heared from some of my friends...that SAS - 9 supports PARTITION of SAS datasets. I tried for getting syntax and some details, but couldn't able to get. Is anyone has any idea about the partitions of SAS datasets, if so can any one help me out on this? Thanks in advance. Chandu. ________________________________________________________________________ Check out AOL.com today. Breaking news, video search, pictures, email and IM. All on demand. Always Free. ...

Re: SAS Advanced Programming Exam for SAS 9: SAS Joke of the year. #9
ALan , Lets keep this to straight SAS, I dont tell people what they should use in SAS to produce the report, but rather I say here is what the report should look like, here i sthe data set, here ar the specs, now go make it happen. If your hirng a junior level programmer they should know the data step and say proc sort, proc print, proc format. If your going after a Senior level programmer the test should be harder and reflect more things like ODs, macro, etc... In your case you dont promote straight SAS solutions and that is great, but a whole other market than a straight SAS programmer. Toby Dunn Comprimise is like telling a lie, it gets easier and easier. Each comprimise you make, that becomes your standard. Perfection doesnt exist, once you reach it, its not perfect anymore. It means something else. From: Alan Churchill <savian001@GMAIL.COM> Reply-To: Alan Churchill <savian001@GMAIL.COM> To: SAS-L@LISTSERV.UGA.EDU Subject: Re: SAS Advanced Programming Exam for SAS 9: SAS Joke of the year. Date: Tue, 4 Sep 2007 15:54:31 -0600 Well Toby, let me ask something then. Since I am not an ODS fan and haven't used proc report/tabulate for some time, would that be an automatic disqualifier since you don't allow reference books or materials? SAS does not provide tools that help me code ODS (except for EG) and therefore a reference material is all I would need. Now, it's not like I haven't used proc report (used it extensively at one time), ...

Re: SAS
Chandu, ken, To be explicit start at http://support.sas.com/rnd/scalability/spde/index.html Russ Lavery and I have a NESUG Paper "An Annotated Guide: The New (8.2), Free & Fast SPDE Data Engine". It will be availiable at http://www.nesug.org/ whenever everyone has general access to papers. Ian Whitlock ================= Date: Mon, 3 Jul 2006 12:40:24 -0400 Reply-To: evilpettingzoo97@AOL.COM Sender: "SAS(r) Discussion" From: Ken Borowiak <evilpettingzoo97@AOL.COM> Subject: Re: SAS - 9; Partition of SAS Datasets. Comments: To: chandu.isi@GMAIL.COM In-Reply-To: <1151942580.122486.98030@v61g2000cwv.googlegroups.com> Content-Type: text/plain; charset="us-ascii"; format=flowed Chandu, You should be able to find some info in the SPD Engine section of the on-line documentation. HTH, Ken -----Original Message----- From: chandu.isi@GMAIL.COM To: SAS-L Sent: Mon, 3 Jul 2006 09:03:00 -0700 Subject: SAS - 9; Partition of SAS Datasets. Hi All, Recently I heared from some of my friends...that SAS - 9 supports PARTITION of SAS datasets. I tried for getting syntax and some details, but couldn't able to get. Is anyone has any idea about the partitions of SAS datasets, if so can any one help me out on this? Thanks in advance. Chandu. ...

Re: Deleting SAS Data from a SAS DATASET #9
On Fri, 15 Aug 2008 16:09:46 -0500, Mary <mlhoward@AVALON.NET> wrote: >A view helps on deletes, but I wonder how it affects performance of querying the data- wouldn't storing the data in 24 different locations cause a significant slowdown in perfomance upon querying the data versus having it all in one table that is indexed? If this data is queryied a lot but only deleted once a month, the time in querying (which probably is in peak time) could be much more important than the time in deleting (which could be run when the computer is not busy, such as nights or weekends). hi, good point! but as shown below, you can make a view of multiple datasets having the separate indexes, and where seems to be fine with this. interesting. ran on sas 9.1.3 sp4 on windows. cheers, chang /* test datasets */ data one two; set sashelp.class; ds = "one"; output one; ds = "two"; output two; run; /* separately index on age */ proc datasets lib=work; modify one; index delete age; index create age; modify two; index delete age; index create age; quit; /* make a view of two datasets appended */ proc sql feedback; drop view work.oneTwo; create view oneTwo as select * from one union select * from two order by age; quit; /* where is utilizing the indexes */ options msglevel=i; data sixteenAndOlder; set oneTwo; /* we are using the view */ where age >= 16; run; /* on log INFO: Index Age selected for WHERE clause optimiz...

Re: MS Access and SAS datasets
Use PROC FORMAT with the CNTLOUT option to dump your formats. I don't know about the labels. Access has a "Description" field in its metadata structure, so it's reasonable to expect the labels to end up there. On Mon, 23 May 2005 14:01:18 -0800, David Neal <afdbn@UAA.ALASKA.EDU> wrote: >I'm trying to move several SAS datasets to a single MS Access database. >When I use proc copy to move the data, I get the following note: > > > >NOTE: Copying SCFSAS.PT_MISC to SCFFAS.PT_MISC (memtype=DATA). > >NOTE: SAS variable labels, formats, and lengths are not written to DBMS >tables. > > > >My problem is that I'm interested in keeping the variable labels and the >formats as well. Is it possible for SAS to automatically create the "lookup >tables" from the formats? Also, is there a way to keep the variable labels >when I move from SAS to Access? > > > >David Neal ...

Re: Using SAS with large datasets (linking SAS and Access)
I have very little experience with using this but I have found that if you have SAS Access for PC Products licensed, just as you can issue a libname statement pointing to an Excel workbook, you can also issue one for an Access database. Try doing this and then look at your SAS explorer window where you will see an icon for the Access file and will then be able to look at the Access tables as if they were SAS data sets. Nat Wooding Environmental Specialist III Dominion, Environmental Biology 4111 Castlewood Rd Richmond, VA 23234 Phone:804-271-5313, Fax: 804-271-2977 ben.powell@CLA.CO .UK Sent by: "SAS(r) To Discussion" SAS-L@LISTSERV.UGA.EDU <SAS-L@LISTSERV.U cc GA.EDU> Subject Re: Using SAS with large datasets 06/23/2008 06:01 AM Please respond to ben.powell@CLA.CO .UK If you haven't already, export the data out of Access asap as mdb operations tend to be several orders of magnitude slower than SAS. Export to tab or csv and import into SAS. The export procedure from Access is relatively painless. If you've already done that and are still facing problems you should provide more info on variabl...

SAS System Viewer 9.1 unable to open SAS datasets ( SAS 9.1.3)
SAS System Viewer 9.1 was able to open datasets that were created by V8 engine (SAS 8.2), but is unable to open datasets that are created with V9 engine (SAS 9.1.3). Does this need SAS System Viewer to be upgraded ? or Something else needs to be done ? In message <0ae08496-acd1-4c40-8828-b88d059c0d0e@f40g2000pri.googlegroups.com>, msiddu2000 <msiddu2000@gmail.com> writes >SAS System Viewer 9.1 was able to open datasets that were created by >V8 engine (SAS 8.2), but is unable to open datasets that are created >with V9 engine (SAS 9.1.3). > >Does this need SAS System Viewer to be upgraded ? >or >Something else needs to be done ? SAS System Viewer 9.1 can: (1) Read SAS v8 data sets created by SAS v8 on Windows or UNIX (2) Read SAS v8 data sets created by SAS v9 on Windows (3) Read SAS v9 data sets created by SAS v9 on Windows SAS System Viewer 9.1 can not: (1) Read SAS v8 data sets created by SAS v9 on UNIX (2) Read SAS v9 data sets created by SAS v9 on UNIX Alternatives: (1) There is a beta version of the CDISC Viewer that can be downloaded from the SAS web site, but it is fragile. (2) There is also a SAS Universal Viewer bundled with SAS v9.2 for Windows. .....Phil Holland -- -------------------------------------------------------- Holland Numerics Ltd 94 Green Drift, Royston, Herts SG8 5BT, UK mobile : +44-(0)7714-279085 email : <NEWS@hollandnumerics.com> URL : http://www.hollandnumerics.com/ ...

Re: MS Access and SAS datasets #6
You are right, the "slightly" was an understatement on my part.(I guess I was being nice.) I believe ACCESS is limited to 256 (or 255 I forget which) columns so I am required to do a bit of reshaping anyway. I will be working with(reshaping) the data in SAS and then move it into ACCESS. I feel much more comfortable tweaking it in SAS and then moving it to ACCESS. David -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Howard Schreier <hs AT dc-sug DOT org> Sent: Tuesday, May 24, 2005 5:26 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: MS Access and SAS datasets I suspect that you don't need a "slightly" different approach. You probably need a significantly different one. Wide tables are clumsy to work with in SAS, but I think in Access the problems will be much more severe. I would think that the occasion of a port from one platform to another provides the opportunity to reshape and streamline. You will probably find it easier to do this before porting, rather than after. On Tue, 24 May 2005 09:26:21 -0800, David Neal <afdbn@UAA.ALASKA.EDU> wrote: >Thanks for the input. Unfortunately, the datasets are quite wide. One >of them, for example, has over 1000 variables (columns). Had I been >involved with the creation of the initial SAS datasets, I would have >suggested a slightly different approach. Since this wasn't the case, >I'm stuck working with things the way they...

Re: MS Access and SAS datasets #5
I suspect that you don't need a "slightly" different approach. You probably need a significantly different one. Wide tables are clumsy to work with in SAS, but I think in Access the problems will be much more severe. I would think that the occasion of a port from one platform to another provides the opportunity to reshape and streamline. You will probably find it easier to do this before porting, rather than after. On Tue, 24 May 2005 09:26:21 -0800, David Neal <afdbn@UAA.ALASKA.EDU> wrote: >Thanks for the input. Unfortunately, the datasets are quite wide. One >of them, for example, has over 1000 variables (columns). Had I been >involved with the creation of the initial SAS datasets, I would have >suggested a slightly different approach. Since this wasn't the case, >I'm stuck working with things the way they are. To complicate things, >ACCESS won't handle tables that wide so I'm having to mess with he data >anyway. Your (and Howard's) suggestions will at least get me going on >the right path. (Maybe I'll just round up some "slave" labor, AKA a >graduate student, to set up all the lookup tables in ACCESS.) > >Thanks again > >David Neal > >Choate, Paul@DDS wrote: >> Hi David - >> >> I agree with Howard that CNTLOUT will give you your formats to develop >> lookup tables in Access. Alternately if your data isn't large and you >> don'...

Re: MS Access and SAS datasets #2
Hi David - I agree with Howard that CNTLOUT will give you your formats to develop lookup tables in Access. Alternately if your data isn't large and you don't care about normal form, you could process your variables through your formats with put statements and create parallel formatted data. In v9 there's VLABEL, VLABELX, and VARLABEL, etc. You can use VLABEL and array all your _numeric_ and then _character_ columns and create a label dataset. There's also the data dictionary which you can query and use the into: command to load a macro, or just dump the labels in a dataset. Personally, I like to use "options VALIDVARNAME=ANY;" and rename my variables as their labels before I port data to external databases, but I'm an analyst, not a programmer, and I can hear several mavens groaning in the distance as I write this. ;-) Good luck and hth - Paul Choate DDS Data Extraction (916) 654-2160 On Mon, 23 May 2005 14:01:18 -0800, David Neal <afdbn@UAA.ALASKA.EDU> wrote: >I'm trying to move several SAS datasets to a single MS Access database. >When I use proc copy to move the data, I get the following note: > > > >NOTE: Copying SCFSAS.PT_MISC to SCFFAS.PT_MISC (memtype=DATA). > >NOTE: SAS variable labels, formats, and lengths are not written to DBMS >tables. > > > >My problem is that I'm interested in keeping the variable labels and the >formats as well. Is it possible for SAS to automatic...

Re: MS Access and SAS datasets #3
Thanks for the input. Unfortunately, the datasets are quite wide. One of them, for example, has over 1000 variables (columns). Had I been involved with the creation of the initial SAS datasets, I would have suggested a slightly different approach. Since this wasn't the case, I'm stuck working with things the way they are. To complicate things, ACCESS won't handle tables that wide so I'm having to mess with he data anyway. Your (and Howard's) suggestions will at least get me going on the right path. (Maybe I'll just round up some "slave" labor, AKA a graduate student, to set up all the lookup tables in ACCESS.) Thanks again David Neal Choate, Paul@DDS wrote: > Hi David - > > I agree with Howard that CNTLOUT will give you your formats to develop > lookup tables in Access. Alternately if your data isn't large and you > don't care about normal form, you could process your variables through your > formats with put statements and create parallel formatted data. > > In v9 there's VLABEL, VLABELX, and VARLABEL, etc. You can use VLABEL and > array all your _numeric_ and then _character_ columns and create a label > dataset. > > There's also the data dictionary which you can query and use the into: > command to load a macro, or just dump the labels in a dataset. > > Personally, I like to use "options VALIDVARNAME=ANY;" and rename my > variables as their labels before...

Re: MS Access and SAS datasets #8
Does SQL Server Express have a lot of proprietary extensions to the SQL language which provide array processing and the like? If not, the column capacity may be more a curse than a blessing. I don't know the specifics of David's project, but based on experience I suspect that a lot of normalization is possible, and that if it is done, even the capacity of Access will be far more than adequate. On Tue, 24 May 2005 20:07:03 -0600, Alan Churchill <SASL001@SAVIAN.NET> wrote: >David, > >I believe SQL Server Express (which is free) can handle 1024 columns. You >may want to consider that approach if you have to move it anyway. > >Thanks, >Alan > >Savian >"Bridging SAS and Microsoft Technologies" > >-----Original Message----- >From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of David >Neal >Sent: Tuesday, May 24, 2005 6:54 PM >To: SAS-L@LISTSERV.UGA.EDU >Subject: Re: MS Access and SAS datasets > >You are right, the "slightly" was an understatement on my part.(I guess I >was being nice.) >I believe ACCESS is limited to 256 (or 255 I forget which) columns so I am >required to do a bit of reshaping anyway. I will be working with (reshaping) >the data in SAS and then move it into ACCESS. I feel much more comfortable >tweaking it in SAS and then moving it to ACCESS. > >David > >-----Original Message----- >From: SAS(r) Discussion [mailto:SAS-L@LISTS...

Re: MS Access and SAS datasets #4
MS Access also has a CAPTION field that behaves more like a SAS variable label. However, I have not found a way to write to that field from SAS. Ed Edward Heaton, SAS Senior Systems Analyst, Westat (An Employee-Owned Research Corporation), 1600 Research Boulevard, RW-3541, Rockville, MD 20850-3195 Voice: (301) 610-4818 Fax: (301) 610-5128 mailto:EdHeaton@Westat.com http://www.Westat.com -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Howard Schreier <hs AT dc-sug DOT org> Sent: Tuesday, May 24, 2005 11:21 AM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: MS Access and SAS datasets Use PROC FORMAT with the CNTLOUT option to dump your formats. I don't know about the labels. Access has a "Description" field in its metadata structure, so it's reasonable to expect the labels to end up there. On Mon, 23 May 2005 14:01:18 -0800, David Neal <afdbn@UAA.ALASKA.EDU> wrote: >I'm trying to move several SAS datasets to a single MS Access database. >When I use proc copy to move the data, I get the following note: > > > >NOTE: Copying SCFSAS.PT_MISC to SCFFAS.PT_MISC (memtype=DATA). > >NOTE: SAS variable labels, formats, and lengths are not written to DBMS >tables. > > > >My problem is that I'm interested in keeping the variable labels and >the formats as well. Is it possible for SAS to automatically create the "lookup >ta...

Re: MS Access and SAS datasets #7
David, I believe SQL Server Express (which is free) can handle 1024 columns. You may want to consider that approach if you have to move it anyway. Thanks, Alan Savian "Bridging SAS and Microsoft Technologies" -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of David Neal Sent: Tuesday, May 24, 2005 6:54 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: MS Access and SAS datasets You are right, the "slightly" was an understatement on my part.(I guess I was being nice.) I believe ACCESS is limited to 256 (or 255 I forget which) columns so I am required to do a bit of reshaping anyway. I will be working with(reshaping) the data in SAS and then move it into ACCESS. I feel much more comfortable tweaking it in SAS and then moving it to ACCESS. David -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Howard Schreier <hs AT dc-sug DOT org> Sent: Tuesday, May 24, 2005 5:26 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: MS Access and SAS datasets I suspect that you don't need a "slightly" different approach. You probably need a significantly different one. Wide tables are clumsy to work with in SAS, but I think in Access the problems will be much more severe. I would think that the occasion of a port from one platform to another provides the opportunity to reshape and streamline. You will probably find it easier to do this before porting, rather than after. ...

Re: SAS/ACCESS
Does the DBMAX_TEXT option do what you want? http://support.sas.com/onlinedoc/913/getDoc/en/acreldb.hlp/a003113591.htm -- Jack Hamilton jfh@alumni.stanford.org Videtis illam spirare libertatis auram On Jan 22, 2009, at 8:57 am, Matthew Pettis wrote: > Hi, > > > > I have a CLOB coming back from an Oracle passthrough query that is > >1024 > in length. How do I specify that my receiving variable in a SAS > dataset > be longer than 1024 characters to accommodate this? By default, I get > SAS thinking that this is 1024 characters, when it is really a CLOB > and > I want to set some large default length on this variable length... > > > > Thanks, > Matt ...

Re: SAS/ACCESS
DBMAX_TEXT does the trick; thank you all who helped! Matt -----Original Message----- From: Jack Hamilton [mailto:jfh@stanfordalumni.org] Sent: Sat 1/24/2009 1:42 AM To: Pettis, Matthew (Prof II&RS) Cc: SAS-L@LISTSERV.UGA.EDU Subject: Re: [SAS-L] SAS/ACCESS - Oracle: setting field lengths in SAS datasets returned from passthrough Does the DBMAX_TEXT option do what you want? http://support.sas.com/onlinedoc/913/getDoc/en/acreldb.hlp/a003113591.htm -- Jack Hamilton jfh@alumni.stanford.org Videtis illam spirare libertatis auram On Jan 22, 2009, at 8:57 am, Matthew Pettis wrote: > Hi, > > > > I have a CLOB coming back from an Oracle passthrough query that is > >1024 > in length. How do I specify that my receiving variable in a SAS > dataset > be longer than 1024 characters to accommodate this? By default, I get > SAS thinking that this is 1024 characters, when it is really a CLOB > and > I want to set some large default length on this variable length... > > > > Thanks, > Matt ...

Re: Converting from SAS 5 to SAS 9 #9 1545842
I believe DOS is not the MS-DOS you're thinking of; it was one of IBMs mainframe operating systems (the other system at the time would have been OS --> MVS --> z/OS). Unless written in transport, you'll need a mainframe to read them. ---- Original message ---- >Date: Fri, 17 Dec 2004 19:52:28 +1300 >From: Robin Templer <robin.templer@XTRA.CO.NZ> >Subject: Re: Converting from SAS 5 to SAS 9 >To: SAS-L@LISTSERV.UGA.EDU > >AH ... - then you do have an issue and I suspect a mission. > >1. SAS V5 never ran in the DOS or Windows environment - so I suspect >that you DO NOT have V5 datasets. You need to ascertain exacly under >WHICH environment and Version of SAS the data was created under. What >are the file extensions of the datasets - that may well tell us the >answer. If they are dataset.SSD then they are DOS or Windows V6 >datasets and you will be able to read them with SAS 9. > >2. Secondly - I remember that Proc V5TOV6 was not available on the PC >platforms (DOS and Windows and OS/2) as there had never been a V5 >release in those enviornments - it was only available on VMS, MVS, CMS etc. > >Until you know the answer to point 1, then I suspect all we can offer >are guesses > > >Al Nardi wrote: > >>Ah...thats the issue..it was created on a (sit down again) a DOS system.. >>the user emailed me 4 small versions 5 files...and my task is to convert >>them.. >&...

Re: SAS Advanced Programming Exam for SAS 9: SAS Joke of the year.
I took the advanced exam this April because I wanted a relatively systematic way of assessing my knowledge of SAS in a short time span. For that purpose, it was worth it. Since I learn SAS by doing new tasks, or re-doing old tasks in a new way, I assume my knowledge of SAS is uneven, even though I am regarded as productive, and frequently creative in using SAS to solve our group's problems. I passed the test, with lower subscores on the components that I expected to be weakest on. I thought many of the questions made me think about some fundamental, sometimes subtle, features of the language. I did some guessing, but that was on my weaker topics. So the exam results, in my view, reflected something real. I agree, a prospective employer should not put much stock in SAS certification exams. Many highly effective people are not good test takers. Besides, this exam is a crude instrument. My score was identical to a colleague who still regularly asks me for guidance in finding solutions in SAS to specific problems. I probably know more SAS than he does (and he is a good SAS programmer), but you wouldn't know from the exam results. As to version 9-specific questions, I don't recall whether there was much material that was version 9 only. But I expected the test to be more oriented to "advanced" concepts than to new features of version 9. By the way, even though I passed, I can't get a SAS advanced certificate -- because I haven't taken the...

Re: Converting from SAS 5 to SAS 9 #9 641267
I did a little googling tonight and came across some SAS faqs about converting V5 files to V6. It seems that Proc V5toV6 was available on most platforms but not on the pc. However, there is supposed to be a V5 engine available that will allow SAS V6 to read a V5 file. Nat ...

Re: combine n SAS datasets in to one SAS dataset.
If you use the dictionary tables try Proc SQL - it will run much more quickly than a datastep: %let lib=YourLib; %let mem=file2007; proc sql noprint; select MemName into :MemList separated by " &lib.." from dictionary.tables where LibName=upcase("&lib") and MemType='DATA' and MemName eqt upcase("&mem"); quit; data &lib.File_History; set &lib.&MemList; run; hth Paul Choate DDS Data Extraction (916) 654-2160 -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of stulkem@YAHOO.COM Sent: Thursday, January 17, 2008 12:06 PM To: SAS-L@LISTSERV.UGA.EDU Subject: combine n SAS datasets in to one SAS dataset. Thanks for your help in advance! I have hundreds of SAS datasets that I want to combine into one SAS dataset. For example, I want to set file20070101.sas7bdat - file20071231.sas7bdat (365 total files) into file_history.sas7bdat. How can I write this into a macro or array or whatever will work so I don't have to write each individual file name?? Thanks again! Mark ...

Re: SAS Advanced Programming Exam for SAS 9: SAS Joke of the year. #2
jontugman, Test preparation is akin to following a simple algorithm: 1. Evaluate the test and discover if it is worth taking. 2. If #1 evaluates false then go to exit. 3. Determine if your *test* knowledge of SAS is insufficient. 4. If #3 evaluates true, do the test preparation. 5. Pay the money. 6. Take the test. 7 Exit. From your standpoint, the step of paramount importance is step #1. That is where you mainly failed. From SAS' standpoint, only one step matters: #5. This is the only reason the test was created in the first place. The world would be a better place if all employers understood that as well. However, some recruiters/HRers require the certificate as a CYA backup should they accidentally hire a pure test-passer. Fortunately, I have not seen many occurrences of this nature since the inception of the boondoggle, perhaps because most candidates are almost inevitably interviewed by people qualified in SAS better than HR. And most qualified people saw the program for what it is even before its advent. SAS-L is replete with numerous posts to prove it. Needless to say, it does not imply in any way that any certificate-holder has no more SAS behind the belt than the certificate can cover. Far from that! Many fantastic real-world people have been forced into the thing by their SAS partnership business needs, many have taken it just for the heck of it because their employer would pay for it, etc. My opposition to the thing as a matter of principle is based on t...

Re: SAS Advanced Programming Exam for SAS 9: SAS Joke of the year. #5
Good deal Bob, atleast that company was headed in the right direction IMO... I have given such tests and taken them. I ussually give them a data set, the specs I want them to follow, and a example of what I want the output to look like. Then I tend to give them like 4 or 5 hours if they need it to complete the project. In reallity they should be done in an hour or so. The test should be challenging but not too challenging, and the solution should involve a few data steps, procedures, and some type of reporting..... Toby Dunn Comprimise is like telling a lie, it gets easier and easier. Each comprimise you make, that becomes your standard. Perfection doesnt exist, once you reach it, its not perfect anymore. It means something else. From: Bob_Abelson@HGSI.COM Reply-To: Bob_Abelson@HGSI.COM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: SAS Advanced Programming Exam for SAS 9: SAS Joke of the year. Date: Tue, 4 Sep 2007 17:22:59 -0400 I interviewed at a company that gave a test where I had a half hour to produce a very simple report using PROC REPORT. I was provided all the manuals I wanted, but because I had used PROC REPORT before, I wanted none of them. I finished in five minutes, and most people on SAS-L would be able to beat that time. Bob Abelson HGSI 240 314 4400 x1374 bob_abelson@hgsi.com "toby dunn" <tobydunn@HOTMAIL.COM> Sent by: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU> 09/04/2007 05:15 PM Please respond to "toby d...

Re: SAS Advanced Programming Exam for SAS 9: SAS Joke of the year. #6
I interviewed at a company that gave a test where I had a half hour to produce a very simple report using PROC REPORT. I was provided all the manuals I wanted, but because I had used PROC REPORT before, I wanted none of them. I finished in five minutes, and most people on SAS-L would be able to beat that time. Bob Abelson HGSI 240 314 4400 x1374 bob_abelson@hgsi.com "toby dunn" <tobydunn@HOTMAIL.COM> Sent by: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU> 09/04/2007 05:15 PM Please respond to "toby dunn" <tobydunn@HOTMAIL.COM> To SAS-L@LISTSERV.UGA.EDU cc Subject Re: SAS Advanced Programming Exam for SAS 9: SAS Joke of the year. Ed , I still contend and stick with they should both be able to program and know how SAS works. I prefer the intervewing company give a test, were the person being interviewed is sat in front a laptop or desktop and told to write code to solve some problems. No online help no books just the persona nd the computer. This weeds out those who can code and those who cant, from those who can you then talk to them about the code they wrote and you can deduce those who understand how SAS works and thos who dont. The pool you are left with are the qualified candidates atleast from a SAS perspective and you can make your choice from there. Toby Dunn Comprimise is like telling a lie, it gets easier and easier. Each comprimise you make, that becomes your standard. Perfection doesnt exist, once...

Web resources about - Re: MS Access and SAS datasets #9 - comp.soft-sys.sas

Data set - Wikipedia, the free encyclopedia
For IBM mainframe term for a file, see Data set (IBM mainframe) . For the telecommunications interface device, see Modem . A dataset (or data ...

Data : Where can I get large datasets open to the public?
Answer (1 of 91): Here's the ones I've found most useful: CrunchBase, US Census, Google Public Data, Infochimps, Timetric, Factual, Freebase, ...

YouTube - Hans Rosling: Let my dataset change your mindset
Hochgeladen am 31.08.2009 http://www.ted.com Talking at the US State Department this summer, Hans Rosling uses his fascinating data-bubble software ...

The Mindset, Skillset, Dataset Approach to Social Media
... Social media is comprised primarily of unstructured data, which is difficult to analyze. A new approach called Mindset, Skillset, Dataset can ...

Sending large datasets to Amazon? Use the Post Office
Amazon has introduced a new method to move large amounts of data to and from …

The Full Dataset on What VCs are Thinking About Funding in 2016
... challenging and many other startups were cutting costs (as many of ours has done in late 2015). We promised that we would clean up the dataset ...

Yahoo Releases the Largest-ever Machine Learning Dataset for Researchers
Yahoo is announcing the public release of the largest-ever machine learning dataset to the research community.

IDG Contributor Network: Are datasets truly anonymized? Two well-suited researchers are going to find ...
With little fanfare or formality, Adam Smith , associate professor of computer science and engineering in Penn State's School of Electrical Engineering ...

House GOP looks to shed light on EPA secret datasets
House Republicans have introduced a bill that would block the Environmental Protection Agency from crafting regulations based on “secret” scientific ...

Guest Contribution: “Capital Control Measures: A New Dataset”
Today we are pleased to present a guest contribution written by Andrés Fernández (IDB), Michael W. Klein (Tufts), Alessandro Rebucci (Johns Hopkins ...

Resources last updated: 3/18/2016 8:15:56 PM