Configuring the Sybase Entity Framework Data Provider
- Last Updated: April 16, 2026
- 4 minute read
- ADO.NET
- Documentation
The Sybase Entity Framework data provider is based on the standard Sybase ADO.NET data provider. See The Sybase Data Provider for detailed information on information common to both types of Sybase data providers. However, because of functionality that is provided by the ADO.NET Entity Framework, some configuration differences are required.
You can configure specific behavior for the data provider in several ways:
- By tuning behavior with a connection string. See Configuring Connection String Options for more information.
- By adding the modifying the storage model file of an Entity Data Model. See Adding the Provider Schema Attribute for more information.
- By modifying the appropriate configuration file using a text editor. For example, you can add options to filter which schema objects to return, configure the data provider's interaction with the .config file, and enable the Logging application block. See Modifying the Configuration File for more information.
Adding the Provider Schema Attribute
Provider is an attribute of the Schema element in the storage model file of an Entity Data Model (EDM). The storage model file is written in the store schema definition language (SSDL).
The Entity Data Model wizard assigns the value when you select the Sybase data provider. If you are manually defining an EDM, assign the string DDTek.Sybase to the Provider attribute of the Schema element, as shown in the following example for Sybase 15:
<Schema Namespace="AdventureWorksModel.Store" Alias="Self" Provider="DDTek.Sybase" ProviderManifestToken="Sybase15 xmlns:store="https://schemas.microsoft.com/ado/2007/12/edm/EntityStoreSchemaGenerator" xmlns="https://schemas.microsoft.com/ado/2006/04/edm/ssdl">
Modifying the Configuration File
The Entity Framework data provider defines a number of configuration options that enable you to customize the behavior of the data provider to meet your functional or performance needs. Configuration options are defined in configuration files. The following table summarizes the characteristics of configuration files in which you may want to specify options.
Configuration File Characteristics
| Options | How It is Used | Applications Affected |
| Machine.config | Can affect the model design and application runtime behavior. The product Installer specifies many of the default configuration values in this file. |
All applications running on the machine |
| devenv.exe.config | Can affect how Visual Studio wizards create or update Entity Framework models. | Visual Studio and its wizards |
| EdmGen.exe.config | Can affect how the command-line EDM Generator tool works with Entity Framework model and mapping files. | EdmGen tool |
| App.config Web.config |
Can affect the runtime behavior of your application. | Can affect the runtime behavior of your application |
The following table provides the typical locations for the configuration files.
Location of Configuration Files
| Configuration File | Location |
| Machine.config | Various locations under the %SystemRoot% directory. For example,
The location that is used depends on the Framework version and platform being targeted by your application |
| devenv.exe.config | C:\Program Files (x86)\Microsoft Visual Studio 15.0\Common7\IDE |
| EdmGen.exe.config | Various locations under the %SystemRoot% directory. For example:
|
| App.config Web.config |
In your Visual Studio project Refer to the DataDirect Connect Series for ADO.NET Distribution Guide for information about deployed applications. |
The following code fragment shows the syntax and default values:
<ddtek.sybase.entity
edmSchemaRestrictions="User"
EnableLoggingApplicationBlock="False"
/>
The following table lists the mapping of the configuration file options to their default values.
Options for the Sybase Configuration File
| Option | Default Value |
| edmSchemaRestrictions | User |
| enableLoggingApplicationBlock | False |
| labAssemblyName | Microsoft.Practices.EnterpriseLibrary.Logging, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL |
| labLogEntryTypeName | Microsoft.Practices.EnterpriseLibrary.Logging.LogEntry |
| labLoggerTypeName | Microsoft.Practices.EnterpriseLibrary.Logging.Logger |
The following configuration option descriptions are listed alphabetically.
edmSchemaRestrictions
Description
Restricts or expands the database objects available to you when generating a model from a database. The option filters the schema objects that are returned when building the EDM that your application includes. Restricting the objects can also provide a performance improvement.
You can add or install the EdmSchemaRestrictions option entry in the app.config or web.config file.
Building large models with the Entity Data Model (EDM) can be very inefficient. For optimal results, consider breaking up a model when it has reached 50 to 100 entities. In addition, carefully consider which objects are actually needed in the model.
Valid Values
User | Accessible | AccessibleExcludingList
When set to User, the data provider limits the objects available for the model to those for which the current user is the owner.
When set to Accessible, the model is built against a larger subset.
When set to AccessibleExcludingList, all the schema objects for which the current user has access are returned, less a predefined list of system-related schema.
Default
User
enableLoggingApplicationBlock
Type
Attribute
Description
Enables the Logging Application Block. Refer to the DataDirect Connect Series for ADO.NET Reference for information on using Logging Application Blocks.
Valid Values
True | False
When set to True, the Logging Application Block is enabled.
Default
False
labAssemblyName
Type
Attribute
Description
Specifies the version of the Enterprise Library Logging Application Block. By default, the Entity Framework data providers use the Enterprise Library 6.0 Logging Application Block.
Note: If you are using any version of the LAB other than the Microsoft Enterprise Library 6.0 binary release, you must set the labAssemblyName. For example, if you are using an older or newer version of the LAB, or a version that you have customized, you must specify a value for labAssemblyName.
Valid Values
string
where string is the name of the Enterprise Library Logging Application Block that you want to use.
Default
The Enterprise Library 6.0 Logging Application Block:
Microsoft.Practices.EnterpriseLibrary.Logging, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
labLogEntryTypeName
Type
Attribute
Description
Specifies the LogEntry type name for the LogEntry object.
Valid Values
string
Where string is the LogEntry type name.
Default
Microsoft.Practices.EnterpriseLibrary.Logging.LogEntry
labLoggerTypeName
Type
Attribute
Description
Specifies the Logger type name for the Logging Application Block.
Valid Values
string
Where string is the LoggerType name.
Default
Microsoft.Practices.EnterpriseLibrary.Logging.Logger