Converting Default Base SAS Engine Data Sets to SPD Engine Data Sets

You can convert existing default Base SAS engine data sets to SPD Engine data sets using the following methods: Some limitations apply. If your default Base SAS engine data set has integrity constraints, then the integrity constraints are dropped when the data set is created in the SPD Engine format. The following chart of file characteristics indicates whether the characteristic can be retained or dropped or if conversion results in an error.

* If the default Base SAS engine data set has both compression and encryption, the compression is dropped but the encryption is retained. SAS retains the security of the data set instead of the compression.

To create an SPD Engine data set from an existing default Base SAS engine data set, you can simply use the COPY procedure. The PROC COPY statement copies the default Base SAS engine-formatted data set Local.Racquets to a new SPD Engine-formatted data set Sport.Racquets:

libname sport spde 'conversion_area';

proc copy in=local out=sport;
   select racquets;
run;

Even though the indexes on the default Base SAS engine data set are automatically regenerated as SPD Engine indexes (both .hdx and .idx files), they are not created in parallel because the data set option ASYNCINDEX=NO is the default.

If an SPD Engine data set is encrypted, only the data component files are encrypted. The metadata component files and both index component files are not encrypted.

Use the APPEND procedure when you need to specify data set options for a new SPD Engine data set.

The following example creates an SPD Engine data set from a default Base SAS engine data set using PROC APPEND. The ASYNCINDEX=YES data set option specifies to build the indexes in parallel. The PARTSIZE= option specifies to create partitions of 100 megabytes.

libname spdelib spde 'new_data';
libname somelib 'old_data';
proc append base=spdelib.cars (asyncindex=yes partsize=100) 
  data=somelib.cars; 
run;