topic Re: SAS Stored Procs in Developers

SAS Stored Procs

Go — Thu, 28 Apr 2016 15:04:26 GMT

Hi All,

What is the best way to move all the stored procs from SAS9.2 to SAS9.4 as a part of upgrade/promotion ?

Re: SAS Stored Procs

BrunoMueller — Thu, 28 Apr 2016 15:44:43 GMT

I recommend to use the "Export as SAS Package" functionality from within the SAS Management Console.

Also look at Using the Batch Export and Import Tools

Bruno

Re: SAS Stored Procs

Go — Thu, 28 Apr 2016 19:06:40 GMT

I exported the package(one stored proc as a test case), what are the prerequisites to import that in new environment ? there is nothing like storeprocs folder/destination for this 'package/stored proc' to get imported ?

Re: SAS Stored Procs

Timmy2383 — Thu, 28 Apr 2016 19:09:17 GMT

You can technically put it in any folder (just don't put it in a system folder, of course). Start off by putting it in your user folder (i.e. "SAS Folders/User Folders/<your ID>/My Folder")

Re: SAS Stored Procs

Go — Thu, 28 Apr 2016 19:37:41 GMT

I could successfully import to My Folder in SMC & Code to new app server, I can cat te code in the server,its there; but cant execute from EG, below is the error
[cid:image001.png@01D1A163.31B7D320]

"an error occured executing the stored process job "My-Hat", the stored process library failed to provide the execution context. the server failed to start. the launch of the server process filaed becuase of an invalid or inaccessible WORK library. The launch of server SASBaseApp-Stored Process Server for user sassrv failed. Insufficent information provided for a connection to the metadata server"

Re: SAS Stored Procs

Timmy2383 — Thu, 28 Apr 2016 19:35:34 GMT

Can you try attaching the image again? It doesn't look like it came through.

Re: SAS Stored Procs

Go — Thu, 28 Apr 2016 19:38:40 GMT

Just edited my post , please see again, thanks much

Re: SAS Stored Procs

Timmy2383 — Thu, 28 Apr 2016 19:42:55 GMT

Hmm, it's hard to say without knowing the particulars of each environment. You should open the stored process and make sure everything looks correct, particularly the execution server options. It's complaining about the execution context, so that's what you want to look at. Either it runs under the workspace server (which is what EG will default to) or the stored process server (which is what the web app will default to).

Re: SAS Stored Procs

Go — Thu, 28 Apr 2016 20:08:40 GMT

Storedproc properties are just fine in SMC, but when I open in EG and check properties (right click and modify ) it gives attached error, that's where the issue is !!

Re: SAS Stored Procs

Timmy2383 — Thu, 28 Apr 2016 20:13:02 GMT

When you imported the stored process did it ask you to select the target application server? Are you application server contexts called the same thing in the old environment and new environment?

Re: SAS Stored Procs

Go — Thu, 28 Apr 2016 20:15:40 GMT

It's a different App server (target server), I selected target server and location to save code... as I said before I can see the code in "new location/new sas 9.4 app server" !

Re: SAS Stored Procs

Timmy2383 — Thu, 28 Apr 2016 20:17:27 GMT

In SMC did you try right-clicking on the stored process and then selecting "Make Compatible"?

Re: SAS Stored Procs

Go — Wed, 04 May 2016 14:01:16 GMT

Hi timmy,
This is resolved, turns out I had too many issues bringing up pooled workspace and stored process servers,(it was not issue the issue with promotion) I took care of them
Thank you very much for all your help, I learnt a lot !!