[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sas-l
Subject:    Re: Rel 9.2 : Running 64 bit and 32 bit versions
From:       Joe Whitehurst <joewhitehurst () GMAIL ! COM>
Date:       2011-05-31 22:17:20
Message-ID: BANLkTinF5_-o6GZ-kKRN0NnQ-s+s2dE4zw () mail ! gmail ! com
[Download RAW message or body]

Cindy,

Your recommendation might work but it may lead to a library with both 32bit
and 64bit datasets--something that SAS specifically warns against:

Beginning with the second maintenance release of SAS 9.2, libraries migrated
by the migration tools will automatically be
converted to 64-bit.
Libraries not migrated by the tools, or migrated by an earlier release of
SAS 9.2, will not be converted to 64-bit. You can
manually migrate these 32-bit libraries to 64-bit libraries, or you can
access them from SAS 9.2 with CEDA (crossenvironment data access.)
Manual migration with PROC MIGRATE is recommended rather than CEDA because
PROC MIGRATE:
• is a one-time process.
• provides validation tools.
• converts library members to native 64-bit format, so processing will be
faster than it would be with run-time
CEDA processing.
• prevents mixed 32-bit and 64-bit libraries. (Default SAS processing will
output new data files in 64-bit mode,
and a mixed library is not optimal, because you can accidentally write over
an existing 32-bit file if the name
is duplicated.)
• avoids CEDA constraints. For example, CEDA does not read SAS catalogs
(which can contain user-defined
formats), indexes, integrity constraints, or audit trails. For a list of
CEDA constraints, see
http://support.sas.com/documentation/cdl/en/lrcon/617222/HTML/default/a002143983.htm#a002118680.
Migrating a SAS Deployment to  Microsoft Windows f

On Tue, May 31, 2011 at 5:44 PM, Durrett, Cindy <
CindyDurrett@fdle.state.fl.us> wrote:

> And in bad netiquette, I'll add a PS to my post - if you have a 32-bit and
> need it to be 64-bit, just use the OUTREP=WINDOWS_64.
>
> -----Original Message-----
> From: Durrett, Cindy
> Sent: Tuesday, May 31, 2011 5:29 PM
> To: 'Berman, Mark'; SAS-L@LISTSERV.UGA.EDU
> Subject: RE: Rel 9.2 : Running 64 bit and 32 bit versions
>
> Ah, my friend, we have had this issue!  We haven't noticed any significant
> performance issues but then we are not super-users.  Our server has a 64-bit
> while our PCs that attach are 32-bit, so we often see the CEDA note.  One
> way we deal with it is to use an OUTREP= option when creating our data sets
> and that makes the issue go away.  We also have formats that are created
> from our 64-bit server that don't play nice with 32-bit data sets.
>
> You can use OUTREP= like this (and check the PROC CONTENTS on the data
> representation line to see the difference).
>
> DATA LIB.NEW32FILE (OUTREP=WINDOWS_32);
> SET LIB.OLD64FILE;
> RUN;
>
> PROC CONTENTS DATA=LIB.OLD64FILE; RUN;
> PROC CONTENTS DATA=LIB.NEW32FILE; RUN;
>
> Hope that helps.
>
> Cindy Durrett
> FDLE/FSAC
> Tallahassee, FL
>
>
> -----Original Message-----
> From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of
> Berman, Mark
> Sent: Tuesday, May 31, 2011 5:02 PM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: Rel 9.2 : Running 64 bit and 32 bit versions
>
> Most of our PC Window machines currently run the 32 bit version of Rel 9.2.
> One programmer was recently changed to the 64 bit version. We've currently
> noticed a note in the Log stating the following when the 64 bit machine
> reads a file created by the 32 bit machine, or conversely when the 32 bit
> machine reads a file created by the 64 bit machine.  Has anyone noticed a
> big degradation in performance in this kind of scenario?
>
> NOTE: Data file is in a format that is native to another host, or the file
> encoding does not match the session encoding. Cross Environment Data Access
> will be used, which might
>      require additional CPU resources and might reduce performance.
> Thanks for any comments to shed light on this.
>
> Mark Berman
> Queensborough Community College
> Bayside, NY 11364
>
[prev in list] [next in list] [prev in thread] [next in thread]