Hello,
i try in Enterprise Guide (EG) to delete_physical an OLAP, that is on another host/environment:
I´m connectet in EG on the DEV-environment and want to delete_physical an OLAP on the TEST-environment with this statement:
options metaserver="TEST-environment" metaport=8888 metaprotocol="bridge" metarepository="foundation" metauser="USER" metapass="PASSWORD" ; %macro _delete_physical_olap; proc olap cube="OLAP-NAME" delete_physical; metasvr host = "TEST-environment" port = 8888 olap_schema = "SASApp - OLAP Schema"; quit; %mend _delete_physical_olap; %_delete_physical_olap;
So what happend:
On the TEST-environment the Metadata-Registration is disabled--> that is what expected -> That´s OK
BUT the physical files on the TEST-environment STILL exists - however the physical files on the DEV-environment are deleted! --> That´s not OK.
Is this statement not correct? Or can "proc olap delete_physical" just disable the Metadata-Registration and NOT the physical files on another host? If so - is there an opportunity to do this?
Thank you very much
Best regards
George
If the physical path in both environments is the same (but on different servers), then the files will be deleted on the server where the process runs, and if the process runs on the dev server, the files there will be gone.
Bottom line: run the process on the intended server, don't try to switch metadata environments on the fly.
If the physical path in both environments is the same (but on different servers), then the files will be deleted on the server where the process runs, and if the process runs on the dev server, the files there will be gone.
Bottom line: run the process on the intended server, don't try to switch metadata environments on the fly.
Hi Kurt,
thanks for the info.
But for me this is an illogical behavior. So i have to run the STP on the intended server.
Thank you
Best regards
George
In the metadata definition, there is only the path stored, without an identification of the server on which it is located. The setup always assumes that you
The SAS process assumes that its environment is consistent. By changing metadata servers mid-process, you undermine that.
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Learn the difference between classical and Bayesian statistical approaches and see a few PROC examples to perform Bayesian analysis in this video.
Find more tutorials on the SAS Users YouTube channel.