0 - 25 of 25 tags for .net data provider team

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 featur

.NET Data Provider for Teradata version 14.11.0.1 (or above) supports integration with Visual Studio 2012 and Visual Studio 2013. This exposes the .NET Data Provider for Teradata objects necessary for development of ADO.NET applications utilizing the Teradata Database within Microsoft Visual Studio 2012 and 2013.

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.

Teradata Database supports Inline and Deferred Large Object Retrieval modes. The LOB retrieval modes control the content of rows and accessibility of LOB columns. 

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.  
 

Support for a new dynamically allocated parameter type (TD_ANYTYPE) is available in Teradata Database 14.0. This Teradata enhancement supports input and result parameter types that may be defined dynamically at execution time. The use of the TD_ANYTYPE data type definition in functions and external stored procedures will be discussed.

This blog outlines the steps to create a SQL Server 2008 (64-bit) R2  Linked Server to the Teradata Database.

The Open Data Protocol (OData) is a protocol to share or exchange data over the web.  The protocol was developed by Microsoft in 2007 as part of the ADO .NET Data Services technology (a.k.a. Project Astoria) for creating and consuming data services using the Web. This protocol became widely used that Microsoft gave the protocol its own identification, named it OData and considered ADO.NET Data Services as the .NET implementation of OData.

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.

TdCommandBuilder class, part  of  the .NET Data Provider for Teradata, generates Insert, Update and Delete commands for a Batch Update. But How can you associate a Transaction with CUD commands given that you have no direct control over the Command generation?

This blog describes how to convert .NET Data Provider for Teradata Learning Examples from C# to VB or C++.

Data Source with Fully Qualified Domain Name can speed up logons plagued with slow "Name to IP-Address resolution". 

In this BLOG I will describe how to register a .NET Data Provider with the ADO.NET   DbProviderFactories Class.

A common question about the Entity Framework(EF) is how to use stored procedures within the framework for insert, update and delete operations. The answer is that leveraging stored procedures for insert, update and delete is actually a built-in capability of EF.

A Stored procedure that is defined in a database can be exposed in a conceptual model in two ways:

The .NET Data Provider for Teradata is integrated with Microsoft's Visual Studio 2005 and 2008.  This article addresses the Visual Studio Server Explorer integration with a Teradata data connection and the various database objects that are supported. 

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

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:

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.

Microsoft Visual Studio DataSet designer generates code (C#/VB.NET) to read data from a .NET Data Provider data source or apply changes to the data source. DataSet designer generates parameterized queries and sets the properties of DbParameter object to the corresponding column data type attributes.

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

Microsoft and Teradata worked together last year to integrate SQL Server Reporting, Analysis and Integration Services with Teradata Database. Some MSDN links that provide additional information:

.NET Framework has a very broad support for Asynchronous operations including a well defined Asynchronous Programming Model. All asynchronous operations are started by invoking a Begin method; later a corresponding End method is invoked to retrieve the result.