See Credential Search Order Rules below

4. Both the source and destination catalogs need to be defined.

5. When there is a wildcard in the source schema or source object names, the destination object name cannot be defined, otherwise an error results.

6. If the destination schema name is not specified, it matches the source schema name for each specific source table. When the destination schema name is specified, then use it whether there is a wildcard or not in the source schema name. If there is a

wildcard in the source schema name, and the destination schema name is specified (such that multiple source schemas are writing tables to a single destination schema), an error appears if there are duplicate objects copied to the destination schema.

7. Use the destination object name as defined. If the destination object name is not defined, it is interpreted as equal to a specific source object name.

8. An asterisk ‘*’ or undefined source schema name or object name is treated as “all”

whether wildEnable is set to TRUE or not.

Parallel copy with multiple nodes:

• When the parameter numCopyNodes is set to >1, multiple grid nodes can connect to SAS Data Agent and concurrently copy data from point A to point B. There is a limit on the number of nodes that can connect simultaneously to SAS Data Agent

depending on the system configuration.

• For parallel processing, the controller retrieves a list of objects that need to be copied first. The object names are distributed in round robin to the copy nodes, which adds the received object name to their own list of objects to be copied. Once all of the objects are assigned, all of the copy nodes begin copying concurrently.

daCopy Examples

In this example, daCopy is used to copy a table from source to destination. The "_"

character in the destination table is interpreted literally because WildEnable is set to FALSE by default.

conopts="(driver=fedsql; CONOPTS=(DSN=TKTSORA_DSN; DSN=TERA_DSN))", remoteDriverOptions="SSL=N;",

In the following example, daCopy is used to create multiple copies in a copyList:

cars_copy1 and cars_copy2. proc cas;

session &sess;

action daCopy submit / server="dataagent", username="dbitest", password="mypasswd", port="25141",

conopts="(driver=fedsql; CONOPTS=(DSN=TKTSORA_DSN; DSN=TERA_DSN))", remoteDriverOptions="SSL=N;",

The daDrop action enables users to drop objects, tables, and files from a specified catalog name or schema.

server string Host name for SAS Data Agent

dataAgentName string SAS Data Agent name registered with CONSUL.

none Yes. Define either

server or dataAgentName

Name Type Description Default Required

pass | password string User password for connecting to SAS

catalog string Specifies the catalog name containing the

schema string Specifies the Schema name containing the

Name Type Description Default Required

wildEscape string Specifies a single escape character for

Notes on the rules that are enforced:

1. See Wildcard Rules below.

2. See Case Sensitivity Rules below.

3. See Credential Search Order Rules below.

4. The catalog needs to be defined.

5. The schema and object names enable wildcard characters to drop multiple objects under multiple schemas.

6. An asterisk ‘*’ or undefined source schema name or object name is treated as “all”

whether wildEnable is set to be TRUE or not.

daDrop Examples

In the first example, tables are dropped using CAS action daDrop. The drop tables action with a wildcard failed because wildForce is set to FALSE.

proc cas;

conopts="(driver=fedsql; CONOPTS=(DSN=TKTSORA_DSN; DSN=BASE_DSN))", remoteDriverOptions="SSL=N;",

In this example, tables are dropped using CAS action daDrop. Using a wildcard of

"cars_", the drop tables action is successful when wildForce is set to TRUE.

proc cas;

conopts="(driver=fedsql; CONOPTS=(DSN=TKTSORA_DSN; DSN=BASE_DSN))", remoteDriverOptions="SSL=N;",

1. Wildcard characters include the underscore (_), which represents a single character, and the percent sign (%), which represents any combination of characters.

2. The wildEnable parameter dictates how wildcard characters are interpreted. See that parameter under each action for a description.

3. To escape a wildcard character, use the character specified via the wildEscape parameter before the wildcard character.

4. Wildcards are not supported in any destination name (catalog, schema, or table) or any catalog name. If a wildcard character is specified and wildEnable=TRUE, then it must be escaped (to make it a literal) or you get an error.

Case Sensitivity Rules

1. The data store determines case sensitivity of objects. For example, BASE is a case insensitive data store and therefore all parameters pertaining to catalog, schema, and object are treated as case insensitive. Oracle is an example of a case sensitive data store.

2. SQL identifiers are quoted when SQL is sent to the data store. This preserves case sensitivity for those data stores that support it.

Credential Search Order Rules

The following rules outline the behavior of credential search order (CSO) in dataAgent actions:

1. Use the user name and password if specified.

2. If user name and password are not specified, use the authenticationDomain if it is specified. When domainCredsRequired is set to True, an error is displayed if no credentials are found for the specified authDomain. When domainCredsRequired is set to False, and no credentials are found, it then retrieves an OAuth token for the CAS session and uses the token to connect to SAS Data Agent.

3. If neither user name, password, nor authenticationDomain are specified, it retrieves an OAuth token for the CAS session to connect to SAS Data Agent.