11-02-2017 01:11 PM
We have an old environment that works in a local machine, this machine only have Enterprise Guide.
Now we have an SAS Server, and we want migrate the actual content to the Server. What is the best mode to do this task?
If i define the same libraries in the server, it's enought? Then, if I import a project in another pc with EG and connected to the SAS server, the project will works?
11-03-2017 02:47 AM
How did you define your libraries in the desktop-only environment? Did you specify them in a global autoexec.sas, or in every EG project?
11-03-2017 03:21 AM
So you have code within a project that assigns libraries? Probably in the autoexec section of the project?
I'd suggest that you pull as many library definitions as you can out of individual projects and make them global, either by writing them into autoexec_usermods.sas files on the server or (preferred nowadays) by defining your libraries in metadata. The obvious advantage of centralized library definitions is the fact that you maintain them in only one place. If you have to shift physical locations, you only have to change one definition. Same if you need to tinker with permissions.
Once the logical framework is set up, move your existing data to the new platform. Use either proc cport/cimport, or SAS/CONNECT if you have that licensed. Create cntlout datasets from existing custom formats, and use those as cntlin files on the server. Still better: make sure that all proc format code is migrated to the server.