0 - 8 of 8 tags for parameters

I am attempting to load a tab delimited file into a table, and I am receiving the following errors:
Row number 6,812 had an error.
Cause = Unexpected number of parameters

Row number 26,237 had an error.
Cause = Unexpected number of parameters

I am attempting to execute a parametrized non-query SQL command using TdCommand.ExecuteNonQuery().  The parameter in question is DbType.DateTimeOffset and TdType.TimestampWithZone; the parameter value was generated using DateTime.Now and appears to be completely defined (as verified via the Visual Studio debugger).

We have a requirement to mask sensitive information being loaded into the tables. Let's say we had the first three groups in place, the fourth one came in as a new requirement, and so had to make a coding change. We currently have logic similar to this.


Case when diagnosis_description like '%psych%' Then 'sensitive info'

Hi Experts,
There is a tpump which is taking 10 hours to process 7000 records, whcih earlier was taking 1 hour..  not sure why its taking 
so long now. the script cotains the normal insert select statement. 
just want to know that is there any optimal parametrs setting for the various TPUMP parameters..

I am trying to use SSRS to pass parameters into a derived table in Teradata. The parameters represent a SQL Server table that is about 1600 rows. 
The join I'm trying is
 JOIN (Select ? (varchar(4)), ? (varchar(4))) as derivedtable (Col1Name, Col2Name) on (Col2Name=TDcol)

The Teradata Named Pipe Access Module (NPAM) provides an inter-process communication link between a writer process (such as FastExport) and a reader process (such as FastLoad). The NPAM can also be used by Teradata Parallel Transporter (TPT) for data transfer.

The reader process will initialize the NPAM module via an Initialization string and this article details the various parameters that are initialized during this process.


I would like to know if there is a way to define and use parameters in BTEQ scripts. The only such feature i am aware of is the "using" feature when importing from files. However, What I would like to do is something like the following:


------ define params

param1 = value1

param2 = value2


The commonly known technique to pass parameters to SQL statements at the system or session level utilizes tables (permanent or global temporary tables).
In this blog post, I'll show better performing techniques for system and user level variables using views and QueryBanding.
These solutions are based on TD13, but can also be used pre-TD13, although performance might be worse.