CAUTION:
Do not
change the external name that is prepopulated for a staged table or
variable unless instructed to do so by a SAS representative.
You should change a
table external name or variable external name only if the data source
has changed the table or variable name that is output in the raw data,
and if the SAS IT Resource Management table or variable external name
has not been updated to reflect that change.
For most adapters, SAS
IT Resource Management uses the external names in order to map the
tables and variables in the raw data to the SAS IT Resource Management
table and column names. For example, previous versions of the Demand
Technologies Performance Sentry collector wrote an object to the log
file as
SQLServer-Locks
. However, in later versions, this object name changed
to
SQLServer:Locks
. In order to process data for the new object, the
external name value for the SAS IT Resource Management table NTSLCKS
should be changed from
SQLServer-Locks
to
SQLServer:Locks
. In the preceding
example, the mapping could not take place and the updated table or
variable could not be processed.
If you expect to process
log files that will contain only the new table or variable external
names, then you can resolve the situation by opening the table properties
and replacing the existing table or variable external name with the
new table or variable external name. (This is a rare situation and
you should change external names only when this particular condition
occurs.)