Page 1 of 1

UniDAC vs SQL SDAC

Posted: Sun 11 Dec 2016 09:43
by MatjazCof
Can someone please clarify what is the difference between SQL Server Data Access Components and Universal Data Access Components.
The price confused me. It is the same, but UniDAC can connect to multiple database where SQL SDAC can connect only to MsSQL server. But the price are the same for both products.
I expect UniDAC would cost more.


Professional Edition with source code
UniDAC Professional Edition + Source Access*
$449.95 $1099.95 $1999.95
vs
Professional Edition with source code
SDAC Professional Edition + Source Access*
$449.95 $1099.95 $1999.95

Re: UniDAC vs SQL SDAC

Posted: Wed 14 Dec 2016 09:33
by azyk
UniDAC allows working with a large number of databases, but it has limited functionality to work with each of them. SDAC allows working only with one database, but it operates with a richer functionality set. In order to balance their functionality/cost ratio, the prices were made the same.

Re: UniDAC vs SQL SDAC

Posted: Wed 14 Dec 2016 09:41
by unidac5src
Thank you.
Do you have compare table which would help me determine what are additional functionalities in SDAC?

Re: UniDAC vs SQL SDAC

Posted: Wed 14 Dec 2016 10:52
by azyk
To access SQL Server, UniDAC uses the same main modules that are used in SDAC. However, UniDAC has no support for some specific SQL Server features, that are supported in SDAC:

- ServiceBroker;
- ChangeNotification;
- the NonBlocking mode, in which an SQL query is executed in a separate thread;
- data types: geometry, geography, hierarchyid, and xml

Therefore, if you don't plan to use SDAC specific features, there is no difference between using SDAC and UniDAC.

Also you can check the feature differences following these links:
https://www.devart.com/unidac/components.html and https://www.devart.com/sdac/components.html