I have two servers registered on SAS. When trying to create a SASUSER table in one server, it allows me and it gets created however on the other server when I try to create a sasuser table i get the following error:
ERROR: Write access to member SASUSER.Mytable
I am using SAS enterprise version and not the university edition.
How can I enable my write accesses on the other server?
Related
I created a Snowflake connection via Power BI Desktop after providing the Server and Warehouse Name; then under Advanced Options I specified the Database and entered the following in the SQL statement text area:
call myStoredProcedureName();
and received a pop-up stating "Unable to connect. We encountered an error while trying to connect. Details: 'Native queries aren't supported by this value'".
This is using Snowflake type connection so what am I missing? If I execute using the same syntax directly in Snowflake, I get the results without any issues.
Forgot to mention that I'm using Import mode, b/c my 1st attempt using Direct mode produced an error clearly stating Direct Mode wasn't supported.
rsubmit;
<Code>
endrsubmit;
This is useful if u are connected to the local server and you want to run a code on the remote. But how do I run a local script from the remote server? Is there something equivalent to localsubmit?
Additional Info:
I run most of my codes on the remote server because it is faster but I need to use the local SAS in two instances
There is one location with lots of space that I am unable to access through the remote server. I.e. it can be accessed as I:\folder1\folder2 but not as /folder1/folder2 (I tried finding a shortcut through filezilla but I guess the IT team has not created it)
Proc export with dbms = excel is only possible with a local server without which I cannot export multiple data in the same excel file (Which leads to a mess and would involve changing set processes/architecture that use dbms = excel)
You can only run code locally (on the machine on which EG installed) if you have a Base SAS licence. You will know this is the case if you open your SAS program (in EG), and check the values in the "Selected Server" dropdown. If you have a 'local' option you can run locally.
There is no concept of localsubmit. If you wanted to run code on your machine and trigger it from the server, your local machine would have to be configured as a SAS/Connect server and you would use rsubmit (with appropriate connection profile) from that server to your local machine. This would be a highly unusual scenario!
If I understand properly, at least for the second example there's a fairly common use case here.
What you'd do is to run the main program in rsubmit, and then in non-rsubmit block download the dataset created from the rsubmit block.
libname rwork slibref=work server=<yourserver>;
See this KB article for more information.
Then you could do it easily:
rsubmit server=myserver;
data class;
set sashelp.class;
run;
endrsubmit;
libref rwork slibref=work server=myserver;
data l_class;
set rwork.class;
run;
proc export data=l_class ...;
run;
Or even skip the l_class dataset and directly export from rwork.
For the first scenario, a large part depends on why you can't just not use rsubmit. Is the program located on the remote server, and you can't directly access it? You'd want to talk to IT I guess to find out how to directly access it.
I'm trying to use an OLEDB connection to connect to my SAS datasets from QlikView.
I am able to set up the connection, but I am not able to load my data. Executing the data import results in the following error: "the local provider does not currently support sql processing"
My loading code looks like this:
LOAD "account",
balance,
"open_closed";
SQL SELECT *
FROM "BASE_DATA";
Is there any way to solve this?
We read SAS data into QlikView using SAS ODBC driver that connects to SAS/SHARE.
This requires that you have one of the following three:
1. SAS/SPD Server
2. SAS/SHARE Server
3. SAS locally on desktop (will not work on server license)
We have a some ETL processes that read CSV files that are output from SAS programs. I'm in the process of upgrading one of these ETLs and was wondering if I could use SSIS to read directly from the SAS dataset.
Has anybody done this successfully?
See here
"You can use SAS Local Data Provider (can be downloaded separately and comes as part of SAS for Windows installation). "
Recently I've moved data from SAS environment:
In connection manager I choose _Native OLE DB\SAS Local Data Provider 9.3_
Enter file name (`\..\dev` before the table name). Click OK
Drag _OLE DB Source_ into the Data Flow
Right click on _OLE DB Source_ and choose _Show advanced editor_
In the first tab (_Connection Manager_) choose _SAS Connection Manager_ from drop down list you created now
In the Component Properties tab in _OpenRowset_ write the name of the table, click OK
If you have `datetime` type transform it using Derived Transformation Editor
For loading SAS XPT or SAS7BDAT data files without having an instance of SAS to connect to via OBDC we used the following
A third party tool (STATTransfer) to read the XPT file
STATTransfer ODBC driver
Setup the connection in SSIS as an ODBC datasource and load into the database for processing.
There are SAS datasource SSIS extension available http://www.cozyroc.com offer a SAS Data connection, but they where outside our price range
I'm using SQL Server 2005 with Reporting Services. I have many reports installed, some using shared data sources and some not; some go to web services, some to sql server databases, and now I'm trying to connect to a DB2 database.
I have successfully created a shared data source and report in Visual Studio 2005. I can pull data just fine and display it on my report in the designer. I am now trying to install the report and datasource through the ssrs web service (the same way I have for all other reports).
The problem is that most of our data sources use Integrated Security, and for this data source I am using 'Credentials are not required' since they are listed in the connection string. Here's my install code:
Dim definition As New ServiceProxy.DataSourceDefinition
definition.ConnectString = connectionStringIncludingUsernameAndPassword
definition.Extension = "OLEDB"
definition.CredentialRetrieval = ServiceProxy.CredentialRetrievalEnum.None
ServiceWebService.CreateDataSource(dataSourceName, containingFolderFromRoot, True, definition, Nothing)
This also works fine and gives no errors, and appears to create the datasource properly in ssrs. But when I go to run the report I get this error:
The current action cannot be completed
because the user data source
credentials that are required to
execute this report are not stored in
the report server database.
(rsInvalidDataSourceCredentialSetting)
My report is properly connected to my data source, and my data source is properly set to credentials not required, so it is all the same as it is inside Visual Studio. I'm out of ideas.
The problem was several fold:
the user name and password were listed in the connection string instead of inside the server
the db2 connect software installed on the report server was out of date (8 instead of 9)
the user group 'DB2Users' did not have any members
After correcting these problems, the report works!