Just emailed my account manager about getting this installed ...  ... View more

Update whilst the libname is syntactical correct it does not appear to work.   If I use the pass through syntax I get error "schema map entry for "tablename" could not be found. Check query syntax and schema map definition and try again."    Any ideas?   Got it working ....   * first get the schema and table names using .... ; proc sql; connect to odbc(DATAsrc=ODBC_DNS_NAME); create table work.odbcSchema as select * from connection to odbc (ODBC::SQLTables); quit; * the output has the schema name labelled as Table_schem and the table_name in my database ; * I got field name from using Microsoft Azure Storage Explore ; proc sql; connect to odbc(DATAsrc=ODBC_DNS_NAME); create table work.SAS_dataset_name as select * from connection to odbc (select fieldName from Table_schem.table_name); quit;   (note :S is actually a colon followed by a S) ... View more

I have managed to get Cosmos DB drivers installed (from CDATA) on my SAS comp server Got a system DSN ODBC connection set up on my SAS comp server (that tests as working) using the URL and token LIBNAME cosmos ODBC DATAsrc=CosmosDBODBCNAME ; (Syntactical works)   But that is as far as I have got.  I do not know what the collections are called on the database.   Has any one found as examples of how to discover what collections are on a Cosmos nosql database?   Not from within SAS but using https://azure.microsoft.com/en-us/features/storage-explorer/   ... View more

Hi Jeff   I am having trouble connecting to an Azure SQL database using the OLE DB drivers.    I can connection to another database on the same server using the same credentials but the database I am trying to connect to has two dashes and a dot in the name for example bitA-bitB-BitC.BitD as the database name. I can use the same credtentials to log directly on the database so the credtentials is not the issue.   This works (different database on the same server): LIBNAME zDEV_tt OLEDB    PROPERTIES="'initial catalog'=databaseName"    PROVIDER=MSOLEDBSQL    DATASOURCE="servername.database.windows.net"    SCHEMA=schemaNameA   USER=UserName    PASSWORD="encoded password" ;   This does not:   LIBNAME zDEV_tt OLEDB    PROPERTIES=('initial catalog'="bitA-bitB-BitC.BitD")   PROVIDER=MSOLEDBSQL    DATASOURCE="servername.database.windows.net"    SCHEMA=schemaNameB    USER=UserName    PASSWORD="encoded password" ;   Any ideas?   Kind Regards   Michelle   PS this is an open track with SAS support at the moment ... View more

That will get us through the firewalls. When we used the network without firewalls it still would not install until we got McAfee to stop working. ... View more

I had the SAS server locking my AD account repeatedly. It was tracked it back to when I tested the SAS studio installation after which I had then changed my password. I did not logon to SAS studio again. The password was changed in the my profile from within SAS EG but somehow SAS would still pick up my old password stored by SAS studio run that against the SAS server and lock my AD account.   Removing the password from the SAS studio saved information worked for me.   Hope that helps.   ... View more