Devart SQL Server Data Access Components (SDAC) 8.2.8 Full Source

1 view

Skip to first unread message

Eva Dunckel

unread,

Aug 21, 2024, 4:38:29 AM8/21/24

to ciablocunath

SQL Server Data Access Components (SDAC) is a library of components that provides access to Microsoft SQL Server databases. SDAC connects to SQL Server directly through OLE DB. The SDAC library is designed to help programmers develop faster and cleaner SQL Server database applications. SDAC is a complete replacement for standard SQL Server connectivity solutions and presents an efficient alternative to the Borland Database Engine for access to SQL Server.

By providing access to the most advanced database functionality, SDAC allows developers to harness the full capabilities of the SQL Server and optimize their database applications. SDAC provides complete support for working with SQL Server Compact Edition, SQL Server queuing and reliable messaging, IRowsetFastLoad interface, working with metadata information, MARS. Get a full list of supported SQL Server features in Features.

Devart SQL Server Data Access Components (SDAC) 8.2.8 Full Source

Download File https://psfmi.com/2A4hp1

The goal of SDAC is to enable developers to write efficient and flexible database applications. The SDAC library is implemented using optimized code and advanced data access algorithms. Component interfaces undergo comprehensive performance tests and are designed to help you write efficient product data access layers. Find out more about using SDAC to optimize your database applications in Increasing Performance.

The SDAC interface retains compatibility with standard VCL data access components like BDE. Existing BDE-based applications can be easily migrated to SDAC and enhanced to take advantage of SQL Server-specific features. Project migration can be automated with the BDE/ADO Migration Wizard. Find out more about Migration Wizard in Using Migration Wizard.

SDAC is an SQL Server connectivity solution that is actively developed and supported. SDAC comes with full documentation, demo projects, and fast (usually within one business day) technical support by the SDAC development team. Find out more about getting help or submitting feedback and suggestions to the SDAC Development Team in Getting Support.

SDAC uses OLE DB, which is a native SQL Server interface, directly through a set of COM-based interfaces to connect to the server. SDAC is designed to be lightweight and consists of a thin layer between your code and SQL Server databases.

Devart is a leading company working in the database connectivity area. It offers well-known native VCL/CLX components and dbExpress drivers for direct access to Oracle, MS SQL Server and MySQL. Devart provides advanced data access solutions for the Microsoft .NET Framework - ADO.NET data providers for native connectivity to Oracle, MySQL and PostgreSQL database servers. It is also a vendor of powerful database tools designed to automate and simplify database development process.

Since upgrading my Delphi subscription from Professional to Enterprise, I've been slowly replacing third-party database components with FireDAC since the Enterprise edition comes with many more databases supported. One of the ones I've used a lot is Devart's UniDAC. UniDAC is a great database component suite. I've used them for many years, they have an excellent support forum, and frequent updates. I just don't want to pay for duplicate functionality--well, mostly duplicate; there are some advantages to using UniDAC but they're not deal-breakers for me.

One of those "not a deal-breaker" advantages is direct database access. Many database vendors require some sort of client-access library or application to be installed in order to access their database. I write a lot of custom applications for Retail Pro 9 which uses an Oracle database on the back end. Each installation of these programs is either on the same server as the Oracle database or on a computer that already connects to the Oracle database. Therefore, I always have the Oracle client already installed. This is key for switching from UniDAC (which offers direct Oracle access) to FireDAC (which requires an Oracle access client installed).

With very little effort, I was able to change the UniDAC components on my data modules to FireDAC components by viewing the data modules as text, doing a textual find-and-replace from TUniQuery to TFDQuery, switching back to form view, saving, then answering Yes to the multiple prompts to correct the corresponding components in the code. This also automatically added the correct FireDAC units I needed and I removed the UniDAC ones I no longer needed--namely, Uni. The connection component was almost as simple and in a shared data module used by all the applications so it didn't take very long.

The only other thing I found I had to do (discovered at runtime) was change several of the fields defined at design-time from the ones UniDAC used to the ones preferred by FireDAC. This simply involved removing the defined fields, activating the new FireDAC query component at design-time, and letting FireDAC add all the fields back in through the Fields Editor. Some (but not all) TStringField entries were replaced with TWideStringField ones; all TLargeIntField, TFloatField, and TSmallIntField were replaced with TBCDField or TFMTBcdField with different Precision and Size values.

Building the installer required another change. These particular applications have to be built with run-time packages so there are several BPLs that must be deployed along with the executable. I'm using Delphi 10.4 Sydney, so instead of Devart's minimum three files for Oracle access, dac270.bpl, unidac270.bpl and oraprovider270.bpl, I need to deploy four FireDAC package files:

These programs have simple database needs, use no stored procedures or special Oracle functions, and do not perform any schema change operations. In fact, all database queries are read-only because of the embedded license used by Retail Pro, so this conversion was relatively straight-forward. If it had been much more complex or if direct database access was really important, the price to renew the second set of database components would've been well worth it.

SQL Server Data Access Components (SDAC) is a library of components that provides native connectivity to SQL Server from Delphi, C++Builder, Lazarus (and Free Pascal) for Windows (both 32-bit and 64-bit) and Mac OS X. SDAC-based applications connect to SQL Server directly through OLE DB, which is a native SQL Server interface. SDAC is designed to help programmers develop faster and cleaner SQL Server database applications.

SDAC, a high-performance and feature-rich SQL Server connectivity solution, is a complete replacement for standard SQL Server connectivity solutions and presents an efficient native alternative to the Borland Database Engine (BDE) and standard dbExpress driver for access to SQL Server.

You can get Source Access to the implementation of all the component classes in SDAC by purchasing the special SDAC Professional Edition with Source Code. The source codes of DataSet Manager and Migration Wizard are not distributed. The source code of SQL Server Direct Mode is distributed obfuscated.