Ready to get started?

Download a free trial of the SAS Data Sets Data Provider to get started:

 Download Now

Learn more:

SAS Data Sets Icon SAS Data Sets ADO.NET Provider

Rapidly create and deploy powerful .NET applications that integrate with SAS Data Sets.

How to Access SAS Data Sets Data Using Entity Framework



This article shows how to access SAS Data Sets data using an Entity Framework code-first approach. Entity Framework 6 is available in .NET 4.5 and above.

Microsoft Entity Framework serves as an object-relational mapping framework for working with data represented as objects. Although Visual Studio offers the ADO.NET Entity Data Model wizard to automatically generate the Entity Model, this model-first approach may present challenges when your data source undergoes changes or when you require greater control over entity operations. In this article, we will delve into the code-first approach for accessing SAS Data Sets data through the CData ADO.NET Provider, providing you with more flexibility and control.

  1. Open Visual Studio and create a new Windows Form Application. This article uses a C# project with .NET 4.5.
  2. Run the command 'Install-Package EntityFramework' in the Package Manger Console in Visual Studio to install the latest release of Entity Framework.
  3. Modify the App.config file in the project to add a reference to the SAS Data Sets Entity Framework 6 assembly and the connection string.

    Set the following connection properties to connect to your SAS DataSet files:

    Connecting to Local Files

    • Set the Connection Type to "Local." Local files support SELECT, INSERT, and DELETE commands.
    • Set the URI to a folder containing SAS files, e.g. C:\PATH\TO\FOLDER\.

    Connecting to Cloud-Hosted SAS DataSet Files

    While the driver is capable of pulling data from SAS DataSet files hosted on a variety of cloud data stores, INSERT, UPDATE, and DELETE are not supported outside of local files in this driver.

    Set the Connection Type to the service hosting your SAS DataSet files. A unique prefix at the beginning of the URI connection property is used to identify the cloud data store and the remainder of the path is a relative path to the desired folder (one table per file) or single file (a single table). For more information, refer to the Getting Started section of the Help documentation.

    <configuration> ... <connectionStrings> <add name="SASDataSetsContext" connectionString="Offline=False;URI=C:/myfolder;" providerName="System.Data.CData.SASDataSets" /> </connectionStrings> <entityFramework> <providers> ... <provider invariantName="System.Data.CData.SASDataSets" type="System.Data.CData.SASDataSets.SASDataSetsProviderServices, System.Data.CData.SASDataSets.Entities.EF6" /> </providers> <entityFramework> </configuration> </code>
  4. Add a reference to System.Data.CData.SASDataSets.Entities.EF6.dll, located in the lib -> 4.0 subfolder in the installation directory.
  5. Build the project at this point to ensure everything is working correctly. Once that's done, you can start coding using Entity Framework.
  6. Add a new .cs file to the project and add a class to it. This will be your database context, and it will extend the DbContext class. In the example, this class is named SASDataSetsContext. The following code example overrides the OnModelCreating method to make the following changes:
    • Remove PluralizingTableNameConvention from the ModelBuilder Conventions.
    • Remove requests to the MigrationHistory table.
    using System.Data.Entity; using System.Data.Entity.Infrastructure; using System.Data.Entity.ModelConfiguration.Conventions; class SASDataSetsContext : DbContext { public SASDataSetsContext() { } protected override void OnModelCreating(DbModelBuilder modelBuilder) { // To remove the requests to the Migration History table Database.SetInitializer<SASDataSetsContext>(null); // To remove the plural names modelBuilder.Conventions.Remove<PluralizingTableNameConvention>(); } }
  7. Create another .cs file and name it after the SAS Data Sets entity you are retrieving, for example, restaurants. In this file, define both the Entity and the Entity Configuration, which will resemble the example below: using System.Data.Entity.ModelConfiguration; using System.ComponentModel.DataAnnotations.Schema; [System.ComponentModel.DataAnnotations.Schema.Table("restaurants")] public class restaurants { [System.ComponentModel.DataAnnotations.Key] public System.String name { get; set; } public System.String borough { get; set; } }
  8. Now that you have created an entity, add the entity to your context class: public DbSet<restaurants> restaurants { set; get; }
  9. With the context and entity finished, you are now ready to query the data in a separate class. For example: SASDataSetsContext context = new SASDataSetsContext(); context.Configuration.UseDatabaseNullSemantics = true; var query = from line in context.restaurants select line;