0 - 4 of 4 tags for no primary index

I have found that when I create a volatile table with say 200million rows where the primary index is explicitely stated and matches the first column in the table, I use much more spool space than if I just let Teradata defined the primary index.   Should, you define a primary index on a volatile table if the index is only on the first column in the temp t

Hi ,
I have a list of 200 stage tables [ truncate and load ] with no primary key defined in SQL Server . Now i need to migrate them to teradata . In that case , shall i go with NO PRIMARY INDEX option or do i need to find its Target table UPI / PI and define the same to Stage as well ? 

Source : SQL Server
Destination : Teradata 13.10
Both Source and Destination tables have NoPI.

I'm a Teradata newbie. I want to create tables with NO PRIMARY INDEX. I am on version 12.0. My DDL looks similar to this.

CREATE MULTISET TABLE UP_KWADA.TEST_INSERT, FALLBACK,
NO BEFORE JOURNAL, NO AFTER JOURNAL, CHECKSUM = DEFAULT
(
LINE_NUMBER DECIMAL(18,0),
TRANSACTION_SET_ID DECIMAL(18,0),
FILE_ID VARCHAR(20)
) NO PRIMARY INDEX ;

I get the error message
3706: Syntax error: Expected something between ')' and the 'NO' keyword.