Database Reference
In-Depth Information
[SalesOrderLineNumber] tinyint NOT NULL,
[RevisionNumber] tinyint NOT NULL,
[OrderQuantity] smallint NOT NULL,
[UnitPrice] money NOT NULL,
[ExtendedAmount] money NOT NULL,
[UnitPriceDiscountPct] float NOT NULL,
[DiscountAmount] float NOT NULL,
[ProductStandardCost] money NOT NULL,
[TotalProductCost] money NOT NULL,
[SalesAmount] money NOT NULL,
[TaxAmt] money NOT NULL,
[Freight] money NOT NULL,
[CarrierTrackingNumber] nvarchar(25) NULL,
[CustomerPONumber] nvarchar(25) NULL
)
WITH
( LOCATION='hdfs://102.16.250.100:5000/files/
HDFS_FactInternetSales'
, FORMAT_OPTIONS
(
FIELD_TERMINATOR = '|'
, STRING_DELIMITER = ''
, DATE_FORMAT = ''
, REJECT_TYPE = VALUE
, REJECT_VALUE = 0
, USE_TYPE_DEFAULT = False
)
);
Looking at the preceding code, you can see that it is indeed more like a
BCP format file than anything else. In addition to the column names, types,
and null-ability, we can also identify the location of both the cluster and the
folder in HDFS holding the data, any field and row terminators, formatting
for dates, both the method and the threshold for rejected records, and we
can see how PDW should handle missing values when importing data using
the USE_TYPE_DEFAULT option.
It is important to note, however, that although it doesn't really behave like
one, an external table is actually a physical table. However, it is not created
Search WWH ::




Custom Search