Using PROC SQL I need to export a file in .sas7bdat format to a library. I can not export the file to my local machine. Using PROC EXPORT no DBMS option works.
Is exporting in this file type possible to my network library?
Thank you
Related
I have a reference to a folder that is on Oracle, but the libraries have already been transferred to the SAS server. I do not know how to add / change to open the file outside Oracle
datafile="&glb_path.\01_projects\credit\_test\RCDT2021.xlsx"
dbms=excel replace;
sheet="RCDTCOD";
getnames=yes;
mixed=yes;
usedate=yes;
scantime=yes;```
This folder is 1: 1 already on shared disc. ```\01_projects\credit\_test\RCDT2021.xlsx"```
I've been using a macro library to find and compile my macro codes until recently, where SAS cannot load the macro.
The code I use is:
options mautosource sasautos=MacLib;
filename MacLib "C:\Users\your.name.here\Documents\Macro_Library";
My macro is saved in the file path above as MacroOne.Sas and I try to run a command in SAS
%MacroOne;
For some reason it is just not compiling anymore, any help?
It was the wrong way around
filename MacLib "C:\Users\your.name.here\Documents\Macro_Library";
options mautosource sasautos=MacLib;
I am using SQLite database and I want to archive database by using SQL Archive Tool (SQLAR) but i don't know how to compile. I found only this document which is given below. Could you help me to compile and use SQLAR Tool to use it ?
https://www.sqlite.org/sqlar/tree?ci=trunk&expand
After these steps are done, i can compress the database.
Download source files. (https://www.sqlite.org/sqlar/vinfo?name=15adeb2f9a1b0b8c)
Copy files to your server.
Write "make" command in your sqlar path which includes source files.
Write command "./sqlar archive_name database_name" to archive your database.
I have trouble with importing both excel and csv files into SAS. It is stored on DropBox on a folder I have locally mapped.
I have tried with:
proc import datafile="C:\Users\Maria\Dropbox\Speciale\skriveri\DATA\sas\csv\prove.xls"
out=data
dbms=xls
replace;
run;
The message in the log is:
ERROR: Physical file does not exist,
C:\Users\Maria\Dropbox\Speciale\skriveri\DATA\sas\csv\prove.xls.
NOTE: The SAS System stopped processing this step because of errors.
I have also tried importing a csv file by replacing xls with csv.
I have checked the path - it's correct and the file names are prove.csv and prove.xls.
I have a 64 bit computer, and tested with SAS 9.3 and 9.2.
I doubt if SAS is able to see the Dropbox folder. Try putting the file in " C:\Users\Maria\" and see what happens.
I added an ODS path statement in the autoexec_usermods.sas on the workspace server like this:
ods path mylibrary.templat(read) WORK.TEMPLAT(UPDATE)
SASUSER.TEMPLAT(READ) SASHELP.TMPLMST(READ);
When I run a SAS 9.2 session on the server I can see that the template store from my library is added to the ODS path as expected.
However, when I start a session from Enterprise Guide 4.2 the ODS path is still the default path. I know the session has included the autoexec_usermods.sas because libraries that are defined there are available in my session. I suspect that Enterprise Guide runs some code in the background when starting a session that resets or defines the ODS path to the default path. I found a macros.sas in C:\Program Files\SAS\Shared Files\Images which contains a ODS TMPLPATH statement but the path defined here is also different from the default. So my guess is this is not the correct file or there is other code executed somewhere.
Any help on this is appreciated.
You can add this statement to the SAS Enterprise Guide options to guarantee that it is submitted when you connect to your SAS server. You can find the option under:
Tools->Options->SAS Programs: "Submit code when connecting to SAS server"
Check the box and add the code that you want to run.
More information at:
http://www.sascommunity.org/wiki/Tips:Project_Specific_Autoexecs_in_Enterprise_Guide