Converting SPD Server 4.x 32-Bit Windows Tables to SPD Server 5.1 64-Bit Windows Tables

Tables that were created with SPD Server 4.x running in Windows 32-bit mode are not compatible with SPD Server 5.1 tables in 64-bit mode. SPD Server 5.1 for 64-bit Windows does not recognize SPD Server 4.x components. If you submit a PROC CONTENTS command to SPD Server 5.1 on a Windows 64-bit server, SPD Server 5.1 does not recognize SPD Server 4.x tables, views, or clusters, even if they exist in a valid SPD Server domain. There are two ways that you can convert SPD Server 4.x tables from a 32-bit Windows environment to SPD Server 5.1 tables for use in a 64-bit Windows environment:

Convert SPD Server 4.x Tables to SAS Tables, Then to SPD Server 5.1 Tables

You can convert SPD Server 4.x tables into SAS 9.2 or SAS 9.3 tables by making a LIBNAME connection to your SPD Server 4.x server, and then making a LIBNAME connection to SAS. After both LIBNAME connections are established, you can use PROC COPY to copy the tables from your SPD Server domain to your SAS domain.

LIBNAME spd44 sasspds “<SPD-Server-4.x-domain-name>”
  host=localhost 
  serv=<SPD-Server-4.x-server-port>  
  user=<user-ID> ;
 
LIBNAME SAS “<path-to-SAS9.2-or-SAS9.3-directory>”;
PROC COPY in=spd44 out=sas;

After you copy your SPD Server 4.x tables into SAS 9.2 or SAS 9.3 tables and store them in a SAS location, you can install SAS 9.4 and SPD Server 5.1 on your Windows 64-bit platform. Next, you use the 64-bit Windows environment to create a SAS 9.4 LIBNAME connection to the directory location where you stored your copied SPD Server 4.x tables, and a SAS 9.4 LIBNAME connection to your SPD Server 5.1 domain. Now you are able to use the SAS 9.4 PROC COPY command to restore the former SPD Server 4.x tables to your SPD Server 5.1 domain in SPD Server 5.1 format.

LIBNAME spd51 sasspds “<SPD-Server-5.1-domain-name>” 
  host=localhost 
  serv=<SPD-Server-5.1-server-port>  
  user=<user-ID> ;

LIBNAME SAS94 “<path-to-SAS9.4-directory>”;

PROC COPY in=SAS94 out=spd51;

SPD Server 5.1 will be able to recognize and use the copied tables in the new SAS 9.4 and SPD Server 5.1 domain space.

Convert Directly from SPD Server 4.x Tables to SPD Server 5.1 Tables

You can convert directly from SPD Server 4.x tables to SPD Server 5.1 tables by using SAS 9.4 with an SPD Server 4.x and an SPD Server 5.1 server. You must be able to operate both versions of SPD Server in your computing environment in order to use this conversion approach.

First, you make two LIBNAME connections using SAS 9.4. You make the first LIBNAME connection to your SPD Server 4.x server, and then you make the second LIBNAME connection to your SPD Server 5.1 server. After you establish a LIBNAME connection between the SPD Server 4.x host and the SPD Server 5.1 host, you can use a PROC COPY statement to copy your SPD Server tables directly from your 4.x host to your SPD Server 5.1 host.

LIBNAME spd44 sasspds “<SPD-Server-4.x-domain-name>” 
  host=localhost 
  serv=<SPD-Server-4.x-server-port>  
  user=<user-ID> ;

LIBNAME spd51 sasspds “<SPD-Server-5.1-domain-name>”  
  host=localhost 
  serv=<SPD-Server-5.1-server-port>  
  user=<user-ID> ;

PROC COPY in=spd44 out=spd51;

Using PROC COPY with SPD Server Clusters

If you use the PROC COPY command to move tables from one SPD Server domain to another SPD Server domain or SAS location, and if your source domain contains tables that use SPD Server clusters, the output file that is produced by the PROC COPY command will be either a SAS table, or an SPD Server table. The output file will not be a clustered table.

To migrate formerly clustered tables from SPD Server 4.x to SPD Server 5.1, you must first undo the table cluster in the source (SPD Server 4.x) location before copying the component tables to the destination (SPD Server 5.1) location.

After the tables are unclustered, you can use PROC COPY to copy the files from the source domain to the destination domain. After you successfully copy your tables to the destination domain, use SPD Server 5.1 CLUSTER TABLE commands to reform the clustered table structures.