0 - 7 of 7 tags for entity provider

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.

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:

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.