You can use the Data Asset node to pull in data from remote data sources that use
connections or from your local computer. First, you must create the connection.
Note for connections to a Planning Analytics database, you must choose a view (not a cube).
You can also pull in data from a local data file (.csv,
.txt, .json, .xls,
.xlsx, .sav, and .sas are supported).
Only the first sheet is imported from spreadsheets. In the node's properties, under
DATA, select one or more data files to upload. You can also drag-and-drop the
data file from your local file system onto your canvas.
Note: You can import a stream (.str) into watsonx.ai that was created in SPSS Modeler
Subscription or SPSS Modeler client. If the
imported stream contains one or more import or export nodes, you are prompted to convert the nodes.
See Importing an SPSS Modeler stream.
Setting data format options
Copy link to section
Different countries use different symbols to separate the integer part
from the fractional part of a number. For example, some countries use a comma (4,5) instead of a
period (4.5). And countries sometimes use different symbols to separate fields in data. For example,
you might use colons or tabs rather than using commas to separate the fields. You can specify which
of these symbols to use. Double-click the node to open its properties and specify data formats.Figure 1. Field delimiter and decimal symbol options
Inferring data structure
Copy link to section
SPSS Modeler processes a sample of the records in the data to
infer the structure of the data and the types of data. Adjust the number for Infer record
count if the first 1000 records are not a good sample for the number of records that you
have. Sometimes, SPSS Modeler can make incorrect inferences about
the structure of the data. For more information, see Troubleshooting SPSS Modeler.
Importing data from an SPSS Statistics file
Copy link to section
If you import data from an SPSS Statistics file (.sav), the following
options are available:
Variable names. Select a method of handling variable names and labels upon
import from an SPSS Statistics .sav file. Metadata that you choose to include
here persists throughout your work inSPSS Modeler and may be exported
again for use in IBM SPSS Statistics.
Read names and labels. Select to read both variable names and labels into
SPSS Modeler. This option is enabled by default, and variable names
are displayed in the Type node. Labels are displayed in charts, model browsers, and other types of
output. By default, the display of labels in output is disabled.
Read labels as names. Select to read the descriptive variable labels from
the SPSS Statistics .sav file rather than the short field names, and use these
labels as variable names in SPSS Modeler.
Values. Select a method of handling values and labels upon import from an
SPSS Statistics .sav file. Metadata that you choose to include here persists
throughout your work in SPSS Modeler and can be exported again for
use in SPSS Statistics.
Read data and labels. Select to read both actual values and value labels
into SPSS Modeler. This option is enabled by default, and the values
themselves are displayed in the Type node. Value labels are displayed in the Expression Builder,
charts, model browsers, and other types of output.
Read labels as data. Select if you want to use the value labels from the
.sav file rather than the numerical or symbolic codes that are used to
represent the values. For example, selecting this option for data with a gender field whose values
of 1 and 2 represent male and female, converts the
field to a string and imports male and female as the actual
values.
It's important to consider missing values in your SPSS Statistics data before you select
this option. For example, if a numeric field uses labels only for missing values (0
= No Answer, –99 = Unknown), then selecting the Read
labels as data option imports only the value labels No Answer and
Unknown and converts the field to a string. In such cases, you should import
the values themselves and set missing values in a Type node.
Use field format information to determine storage. If you deselect this
option, field values that are formatted in the .sav file as integers (such as
fields that are specified as Fn.0 in the Variable View in IBM SPSS Statistics) are imported
using integer storage. All other field values except strings are imported as real numbers.
If you select this option (default), all field values except strings are imported as real
numbers, whether formatted in the .sav file as integers or not.
Read timestamp as date. By default, all timestamp values are shown as
dates. Deselect this option to override this behavior.
Using SQL to pull in data
Copy link to section
In the Data Asset import node properties, under Mode, you can select
SQL Query if you want to use custom SQL to import data from a database. Use
an SQL SELECT statement to pull in rows or columns of data from a database. The
Source path field doesn't apply if you're using the SQL
Query mode.Figure 2. Custom SQL query
The following example pulls in certain rows of data from a database
table:
select * from GOSALES.ORDER_DETAILS
where UNIT_COST > 40,000 LIMIT 4
Copy to clipboardCopied to clipboard
And this example pulls in certain columns of data from a database
table:
select QUANTITY, UNIT_COST, UNIT_PRICE from GOSALES.ORDER_DETAILS
Copy to clipboardCopied to clipboard
The SQL syntax that you use can vary depending on the database platform. For example, if you pull
in data from an Informix database, Informix requires field names to be surrounded by double
quotation marks. For
example:
select "Age", "Sex" from testuser.canvas_drug
Copy to clipboardCopied to clipboard
This SQL feature should only be used to pull in data. Use caution so as not to manipulate the
data in your database.
The following databases currently support this custom SQL feature:
About cookies on this siteOur websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising.For more information, please review your cookie preferences options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.