Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →
LINQ to MongoDB Data
LINQ offers versatile querying capabilities within the .NET Framework (v3.0+), offering a straightforward method for programmatic data access through CData ADO.NET Data Providers. In this article, we demonstrate the use of LINQ to retrieve information from the MongoDB Data Provider.
This article illustrates using LINQ to access tables within the MongoDB via the CData ADO.NET Data Provider for MongoDB. To achieve this, we will use LINQ to Entity Framework, which facilitates the generation of connections and can be seamlessly employed with any CData ADO.NET Data Providers to access data through LINQ.
About MongoDB Data Integration
Accessing and integrating live data from MongoDB has never been easier with CData. Customers rely on CData connectivity to:
- Access data from MongoDB 2.6 and above, ensuring broad usability across various MongoDB versions.
- Easily manage unstructured data thanks to flexible NoSQL (learn more here: Leading-Edge Drivers for NoSQL Integration).
- Leverage feature advantages over other NoSQL drivers and realize functional benefits when working with MongoDB data (learn more here: A Feature Comparison of Drivers for NoSQL).
MongoDB's flexibility means that it can be used as a transactional, operational, or analytical database. That means CData customers use our solutions to integrate their business data with MongoDB or integrate their MongoDB data with their data warehouse (or both). Customers also leverage our live connectivity options to analyze and report on MongoDB directly from their preferred tools, like Power BI and Tableau.
For more details on MongoDB use case and how CData enhances your MongoDB experience, check out our blog post: The Top 10 Real-World MongoDB Use Cases You Should Know in 2024.
Getting Started
See the help documentation for a guide to setting up an EF 6 project to use the provider.
- In a new project in Visual Studio, right-click on the project and choose to add a new item. Add an ADO.NET Entity Data Model.
- Choose EF Designer from Database and click Next.
- Add a new Data Connection, and change your data source type to "CData MongoDB Data Source".
Enter your data source connection information.
Set the Server, Database, User, and Password connection properties to connect to MongoDB. To access MongoDB collections as tables you can use automatic schema discovery or write your own schema definitions. Schemas are defined in .rsd files, which have a simple format. You can also execute free-form queries that are not tied to the schema.
Below is a typical connection string:
Server=MyServer;Port=27017;Database=test;User=test;Password=Password;- If saving your entity connection to App.Config, set an entity name. In this example we are setting MongoDBEntities as our entity connection in App.Config.
- Enter a model name and select any tables or views you would like to include in the model.
Using the entity you created, you can now perform select , update, delete, and insert commands. For example:
MongoDBEntities context = new MongoDBEntities();
var restaurantsQuery = from restaurants in context.restaurants
select restaurants;
foreach (var result in restaurantsQuery) {
Console.WriteLine("{0} {1} ", result._id, result.borough);
}
See "LINQ and Entity Framework" chapter in the help documentation for example queries of the supported LINQ.
Ready to get started?
Download a free trial of the MongoDB Data Provider to get started:
Download NowLearn more:
MongoDB ADO.NET Provider
Rapidly create and deploy powerful .NET applications that integrate with MongoDB document databases.
