Too many options

Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
polsol
Posts: 71
Joined: Sun 20 May 2007 13:29
Contact:

Too many options

Post by polsol » Wed 07 Apr 2010 11:02

1) Why would one choose the standard VCL data access components, Unidac or dbExpress drivers in terms of functionality and performance?

2) With the standard VCL one has to update each VCL driver set (ODAC, IBDAC etc) every time one upgrades one of the VCL sets otherwise there are compatability issues - hence if one has 'the lot' it becomes expensive to do this every time a new feature is added to one of them.
Is the same true of the dbExpress drivers? I guess not if it's just one DLL.
Unidac is a 'once off' upgrade thus at this point seems more cost effective but dbExpress might be better suited to my needs.
Comments?

3) Where does one get the manuals for these products so that one can compare functionality (or learn how to use the trial versions effectively ...). i.e. a link to a 'getting started' guide would be useful.

Dimon
Devart Team
Posts: 2910
Joined: Mon 05 Mar 2007 16:32

Post by Dimon » Thu 08 Apr 2010 07:36

1) It is better to use DAC components because in this case you have access to more server-specific features of SQL servers and higher performance at the expense of direct access to server data without using the dll library, that is required for dbExpress. If you are using DAC components you have many components and specific features, like Dump, MetaData, ChangeNotification, Alerter, SQLMonitor, Local Failover and many other. Also DAC components support server-specific data types.
You can learn more about ODAC features here:
http://devart.com/odac/features.html,
and about IBDAC features here:
http://devart.com/ibdac/features.html.

2) DAC components for different databases have one base level and therefore product compatibility is provided for the current build only. But it takes only few minutes to reinstall the components - just run the .exe installation (you don't need to perform any resettings in your IDE or projects).
UniDAC provides transparent server-independent interface for working with different databases, for example, Oracle, InterBase, SQL Server, and MySQL, but does not include server-specific data providers. You can learn more about UniDAC features here:
http://devart.com/unidac/features.html

3) We will add Getting Started for UniDAC in the next UniDAC build.

polsol
Posts: 71
Joined: Sun 20 May 2007 13:29
Contact:

Post by polsol » Thu 08 Apr 2010 10:07

Dear Dimon,

Many thanks for taking the time to give a comprehensive reply.
My comment on the individual DACS was that if one's subscription has expired and one needs to then just order an update for one of the DACS (or maybe a new DAC that one didn't use previously) then the installation will fail as the older DACS will probably not have the same 'base' units.
Anyway, I guess that UNIDAC Pro is the best choice for my current and future use.

BTW, I think I read that the UNIDAC version of ODAC does not need the client installation. Is this the same as using ODAC Pro in direct mode?
The direct mode in ODAC Pro is the reason I purchased that version in the first instance as Oracle Client will not install correctly on Windows machines that are not Win Pro or above. i.e. will not work on Windows 'home' machines.

Look forward to your 'getting started' manual :wink:

Dimon
Devart Team
Posts: 2910
Joined: Mon 05 Mar 2007 16:32

Post by Dimon » Thu 08 Apr 2010 14:39

Yes, using UniDAC to get access to Oracle server without the client installation is the same as using ODAC in direct mode.

Post Reply