Error message

Warning: Creating default object from empty value in _dxcontentbanner_set_details_blog() (line 206 of /appl1/devx/drupal/sites7/all/modules/devx/modules/dxcontentbanner/
Subscribe to Blog content and comments for dsakai Latest blog posts

This will be part 1 of a multi-part blog about how the .NET Data Provider for Teradata 15.0 can now In-Line Large Objects (LOB)  that are sent to a Teradata Database when executing an INSERT or UPDATE statement.  This first blog will introduce In-Lining of LOB.   Blogs will also be written that discuss how to take advantage of this feature, and performance characteristics.  All these blogs will be more technically oriented than my other blogs.


The XML data type was released in Teradata Database 14.10.  This type enables XML documents and fragments to be stored in a column defined as XML.  Support for the XML type was also added to the  .NET Data Provider for Teradata 14.10 release. 

The Teradata Database supports source files that can reside on the client or server machine that contains Data Definition Language (DDL) to create a function (e.g. stored procedure, user defined function, or user defined type).  The DDL syntax specifies where the file resides and the path to the file.  An example of a DDL to create a stored procedure from a file that resides on the Teradata Database Server is as follows:

The Teradata Database has support for several data types where there is no equivalent Framework Class Library (FCL) type.  For these types, the Teradata Data Provider has a corresonding Provider Specific Type.  All the provider types support:

This is a brief introduction to the new provider specific type called TdNumber .  It will be released in the 14.0 version of the .Net Data Provider for Teradata.  This new type corresponds to the NUMBER data type introduced in 14.0 release of the Teradata Database.  

TdNumber will have similar features/behaviors as the NUMBER data type.  The primary purpose of TdNumber is to allow an application to send and retrieve NUMBER data to and from a Teradata 14.0 or greater database.  It will have the following features and behaviors:

The Entity Provider for Teradata 13.10 did not support the VIEWS and VIEWCOLUMNS store schemas.  Therefore, views were not accessible when using the EDM Wizard.

Starting with the the 13.11 release of the provider, the VIEWS and VIEWCOLUMNS  store schemas are supported.  However, support must be enabled by adding entries into the application configuration file.   This blog explains the steps that are needed to be performed to enable the support for these store schemas so that views can be specified when using the EDM Wizard.

This blog will show you how to retrieve the SQL statement that is generated by the Entity Provider when it processes a  LINQ to Entities or Entity Sql statement.  LinqPad will be used to show you how this can be done.  The blog Using LINQPad to Access Teradata shows how to setup LINQPad to access Teradata.

LINQPad is only able to show the SQL statement that corresponds to a LINQ to Entities or Entity Sql statement when executed against SQL Server.

In this blog I am going to show you how to setup LINQPad v2.26.2 to access a Teradata Database.

LINQPad is a very flexible query tool.  I use LINQPad to primarily execute LINQ to Entities and Entity Sql statements against Teradata when testing the Entity Provider for Teradata.  It is free to use and is available here:

However, you will have to pay for the auto-completion feature.  I highly recommend that you purchase this feature.

Support for the Entity Framework 3.5 SP1 is coming in .Net Data Provider for Teradata (TDNETDP) 13.10. This release of the Data Provider for Teradata includes the Entity Provider for Teradata.

The Entity Provider gets installed during the installation process of TDNETDP. Once installed, applications can be written that execute LINQ to Entities and Entity Sql statements.

In the following examples, an Entity Data Model that references the Northwind database is used. The Northwind EDM and database were created by Microsoft.  These items have been modified for Teradata.

This blog discusses how Query Bands have been implemented in the .Net Data Provider for Teradata

I have placed the Guidelines first because I know many of you are already familiar with Query Bands, and are primarily interested in the guidelines on using Query Bands with the .Net Data Provider for Teradata. If you would like further details refer to the other sections.

Here is a summary of each of the sections: