Skip to content

Unsupported features

Chris Hughes edited this page Jun 30, 2019 · 2 revisions

Features that we will support

High Availability/Disaster Recovery (HA/DR)

Although we plan to add HA/DR support in future, there is no support in the data provider presently. Refer to issue #64.

Unsupported connection string properties

Property Support Notes
AlternateServers TODO A comma-separated list of alternative servers to connect when opening a connection. Format: server:port[,server:port/.../,server:port].
HASession TODO When set to 1 this means we need to operate in a mode which supports failover.
Secondary Data Source TODO Alternative way to specfy an alternative server:port.
Secondary Server Port TODO Alternative way to specfy an alternative server:port.

Unsupported types

Bulk copy

Unsupported connection string properties

Property Support
EnableBulkLoad X

Unsupported types

Features that we won't support

Cursors

ADO.NET doesn't have first-class cursor support, so this feature doesn't appear to be relevant. It's possible that AseClient supported this as a hangover from ADO.

Unsupported connection string properties

Property Support
FetchArraySize X
UseCursor X

Distributed Transactions

Although supported by .NET Framework, .NET Core does not support distributed transactions. As such, there are no plans to implement this feature.

Unsupported connection string properties

Property Support
DistributedTransactionProtocol X
Enlist X
TightlyCoupledTransaction X

Code Access Security

CAS is no longer recommended by Microsoft and will not be supported in .NET Core.

For binary compatibility the following stubs have been added in .NET Core 2.0+ but they do nothing:

  • AseClientPermission
  • AseClientPermissionAttribute

ASE Functions

The SAP Sybase.Data.AseClient provides an AseFunctions type filled with utility functions that aren't implemented. This type will not be supported as it doesn't do anything. Consumers should remove references to this type.