Provider=sas.IOMProvider;Data Source=_LOCAL_;

The value of "_LOCAL_" is a keyword that indicates that a local instance of the IOM servers should be used.

Bridge protocol

Provider=sas.IOMProvider;Data Source=myServerName;SAS Machine DNS Name=lambchop.unx.sas.com;SAS Protocol=2;SAS Port=1359;

Corba protocol

Provider=sas.IOMProvider;Data Source=myServerName;SAS Machine DNS Name=lambchop.unx.sas.com;SAS Protocol=1;SAS Port=1359;

Com protocol

Provider=sas.IOMProvider;Data Source=myServerName;SAS Machine DNS Name=lambchop.unx.sas.com;SAS Protocol=0;SAS Port=1359;

SAS Service Name instead of port number

Provider=sas.IOMProvider;Data Source=myServerName;SAS Machine DNS Name=lambchop.unx.sas.com;SAS Protocol=2;SAS Service Name=sasobjspawn;

Make sure that "SAS Port" isn't defined in the connection string as it will override the "SAS Service Name" value.

Login required by server

Provider=sas.IOMProvider;Data Source=myServerName;SAS Machine DNS Name=lambchop.unx.sas.com;SAS Protocol=2;SAS Port=1359;User ID=myUser;Password=myPassword;

Tabular Data server type

Provider=sas.IOMProvider;Data Source=myServerName;SAS Machine DNS Name=lambchop.unx.sas.com;SAS Protocol=2;SAS Port=1359;SAS Server Type=1;

This is the default setting for server type.

OLAP server type

Provider=sas.IOMProvider;Data Source=myServerName;SAS Machine DNS Name=lambchop.unx.sas.com;SAS Protocol=2;SAS Port=1359;SAS Server Type=2;

Establish communication with an existing workspace

Provider=sas.IOMProvider;Data Source=myServerName;SAS Machine DNS Name=lambchop.unx.sas.com;SAS Protocol=2;SAS Port=1359;SAS Workspace ID=myWorkspaceUniqueIdentifier;

Connects to a unique ID that was generated by the SAS Workspace Manager.

Bridge with host authentication

NOTE! These connection strings are using the "Data Source URI Format" (the "iom-bridge://xx.com:8591" style) which requires SAS version 9.2 or later!

Provider=SAS.IOMProvider;Data Source=iom-bridge://workspace.example.com:8591;User ID=myUsername;Password=myPassword;

COM with host authentication

Provider=SAS.IOMProvider;Data Source=iom-com://workspace.example.com;User ID=myUsername;Password=myPassword;

Bridge with Integrated Windows Authentication (IWA)

Provider=SAS.IOMProvider;Data Source="iom://workspace.example.com:8591;Bridge;SECURITYPACKAGE=Negotiate";

Be careful with the extra quotation marks around the Data Source value (needed because of the semicolon used inside the value).

COM with Integrated Windows Authentication (IWA)

Provider=SAS.IOMProvider;Data Source="iom://workspace.example.com;COM;SECURITYPACKAGE=Negotiate";

Be careful with the extra quotation marks around the Data Source value (needed because of the semicolon used inside the value).

Bridge with a logical server name defined in a SAS Metadata Server and host authentication

Provider=SAS.IOMProvider;Data Source=iom-name://Workspace Server - Logical Server Name;SAS Metadata Location=iom-bridge://metadata.example.com:8561;SAS Metadata User ID=metauserid;
SAS Metadata Password=metapassword;

Bridge with a logical server name defined in a SAS Metadata Server and Integrated Windows Authentication (IWA)

Provider=SAS.IOMProvider;Data Source=iom-name://Workspace Server - Logical Server Name;SAS Metadata Location="iom://metadata.example.com:8561;Bridge;SECURITYPACKAGE=Negotiate";

Be careful with the extra quotation marks around the SAS Metadata Location value (needed because of the semicolon used inside the value).

Logical server name defined in a SAS Metadata Server that is configured via the SAS Integration Technologies configuration utility

Provider=SAS.IOMProvider;Data Source=iom-name://Workspace Server - Logical Server Name;

Use the SAS Integration Technologies configuration utility (ITConfig) to create a configuration file that contains information about how the provider can access the metadata server.

SAS OLAP Data Provider

Bridge protocol

Provider=sas.OLAPProvider;Data Source=lambchop.unx.sas.com;SAS Protocol=2;SAS Port=1359;

Corba protocol

Provider=sas.OLAPProvider;Data Source=lambchop.unx.sas.com;SAS Protocol=1;SAS Port=1359;

Com protocol

Provider=sas.OLAPProvider;Data Source=lambchop.unx.sas.com;SAS Protocol=0;SAS Port=1359;

SAS Service Name instead of port number

Provider=sas.OLAPProvider;Data Source=lambchop.unx.sas.com;SAS Protocol=2;SAS Service Name=sasobjspawn;

Make sure that "SAS Port" isn't defined in the connection string as it will override the "SAS Service Name" value.

Login required by server

Provider=sas.OLAPProvider;Data Source=lambchop.unx.sas.com;SAS Protocol=2;SAS Port=1359;User ID=myUser;Password=myPassword;

Bridge protocol using the "Data Source URI Format"

NOTE! Using the "Data Source URI Format" requires SAS version 9.2 or later!

Provider=sas.OLAPProvider;Data Source=iom-bridge://example.com:1234;

Port number 1234 assumed in the above example string.

Com protocol using the "Data Source URI Format"

Provider=sas.OLAPProvider;Data Source=iom-com://example.com;

The com protocol does not use a port number.

Extract name from the metadata server using the "Data Source URI Format"

Provider=sas.OLAPProvider;Data Source=iom-name://My Logical Name;

Use the SAS Integration Technologies configuration utility (ITConfig) to create a configuration file that contains information about how the provider can access the metadata server.

Extract name from a metadata server defined in connection using the "Data Source URI Format"

Provider=sas.OLAPProvider;Data Source=iom-name://OLAP Server - Logical Server Name;SAS Metadata Location=iom-bridge://metadata.example.com:8561;

Extract name from the metadata server require host authentication using the "Data Source URI Format"

Provider=sas.OLAPProvider;Data Source=iom-name://OLAP Server - Logical Server Name;SAS Metadata Location=iom-bridge://metadata.example.com:8561;SAS Metadata User ID=myUsername;
SAS Metadata Password=myPassword;

Extract name from the metadata server require IWA (Integrated Windows Authentication) using the "Data Source URI Format"

Provider=SAS.OLAPProvider;Data Source=iom-name://OLAP Server - Logical Server Name;SAS Metadata Location="iom://metadata.example.com:8561;Bridge;SECURITYPACKAGE=Negotiate";

Be careful with the extra quotation marks around the SAS Metadata Location value (needed because of the semicolon used inside the value).

Provider=sas.ShareProvider;Data Source=shr1;Location=lambchop.unx.sas.com;User ID=myUsername;Password=myPassword;SAS Server Access Password=myServerPassword;

Specify a server version

Provider=sas.ShareProvider;Data Source=shr1;Location=lambchop.unx.sas.com;SAS Server Release=7;

Default if omitted, the provider uses the SAS 9.1 server access method.

SAS connection strings

SAS IOM Data Provider

Local instance of the IOM server

Bridge protocol

Corba protocol

Com protocol

SAS Service Name instead of port number

Login required by server

Tabular Data server type

OLAP server type

Establish communication with an existing workspace

Bridge with host authentication

COM with host authentication

Bridge with Integrated Windows Authentication (IWA)

COM with Integrated Windows Authentication (IWA)

Bridge with a logical server name defined in a SAS Metadata Server and host authentication

Bridge with a logical server name defined in a SAS Metadata Server and Integrated Windows Authentication (IWA)

Logical server name defined in a SAS Metadata Server that is configured via the SAS Integration Technologies configuration utility

SAS OLAP Data Provider

Bridge protocol

Corba protocol

Com protocol

SAS Service Name instead of port number

Login required by server

Bridge protocol using the "Data Source URI Format"

Com protocol using the "Data Source URI Format"

Extract name from the metadata server using the "Data Source URI Format"

Extract name from a metadata server defined in connection using the "Data Source URI Format"

Extract name from the metadata server require host authentication using the "Data Source URI Format"

Extract name from the metadata server require IWA (Integrated Windows Authentication) using the "Data Source URI Format"

Reuse existing connection using the "Data Source URI Format"

Bridge protocol with host authentication

Bridge protocol with Integrated Windows Authentication (IWA) using the "Data Source URI Format"

Com protocol with Integrated Windows Authentication (IWA) using the "Data Source URI Format"

Using Server ID

Using Server ID and node (network name)

Specifying user and password

Server requires a password

Specify a server version