Sunday, October 4, 2009

SQL Server Data Access Components Overview

CCH : From

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, which is a native SQL Server interface. 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.

SDAC Palette

Advantages of SDAC Technology

SDAC is a direct connectivity database wrapper built specifically for the SQL Server server. SDAC offers wide coverage of the SQL Server feature set and emphasizes optimized data access strategies.

Wide Coverage of SQL Server Features

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 of working with SQL Server 2005 Compact Edition, Service Broker technology, the IRowsetFastLoad interface, working with metadata information, and MARS.

Optimized Code

The goal of SDAC is to enable developers to write efficient and flexible database applications. The SDAC library is implemented using advanced data access algorithms and optimization techniques. Classes and components undergo comprehensive performance tests and are designed to help you write high-performance, lightweight data access layers.

Compatibility with Other Connectivity Methods

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.

How Does SDAC Work?

SDAC allows you to connect to SQL Server through OLE DB, which is the lowest documented SQL Server interface.
SDAC connects through OLE DB through a set of COM-based interfaces. SDAC is designed to be lightweight and consists of a minimal layer between your code and SQL Server databases.
In comparison, the Borland Database Engine (BDE) uses several layers to access SQL Server, and requires additional data access software to be installed on client machines.
The BDE data transfer protocol is shown below.
BDE Connection Protocol BDE Connection Protocol
SDAC allows you to avoid using BDE and DBLibrary.
SDAC Connection Flow SDAC Connection Flow

Key Features

The following list describes the main features of SQL Server Data Access Components.
  • Direct access to server data. Does not require installation of other data provider layers (such as BDE and ODBC)
  • VCL, VCL.NET, and CLX versions of library available
  • Full support of the latest Microsoft SQL Server versions, including Express and Compact Editions
  • Support for all SQL Server data types
  • Disconnected Model with automatic connection control for working with data offline
  • Local Failover for detecting connection loss and implicitly reexecuting certain operations
  • All types of local sorting and filtering, including by calculated and lookup fields
  • Automatic data updating with TMSQuery, TMSTable, and TMSStoredProc components
  • Unicode support
  • Support for many SQL Server-specific features, such as MARS and bulk copy operations
  • Advanced script execution with TMSScript component
  • Support for using macros in SQL
  • Easy migration from BDE and ADO with Migration Wizard
  • Lets you use Professional Edition of Delphi and C++Builder to develop client/server applications
  • Includes annual SDAC Subscription with Priority Support
  • Licensed royalty-free per developer, per team, or per site

SDAC Design-Time View

SQL Data Access Components design time

No comments:

Welcome to Delphi... Delphi... Delphi

I have been a Delphi Developer since Delphi 3 when I finally decided on Delphi in 1996 as my programming language of choice for the Windows 32 environment. So what have I created with Delphi ?

Would you believe that I had single-handedly created a full ERP2 system comprising ERP+CRM where ERP=Sales Distribution+MRP+ Procurement Management+Planning & Production +Finacial Management + Human Resources Management System.

Since 15th February 2009, we have visitors from more than 60 countries including Malaysia, United States, Brazil, Italy, Australia, India, Turkey, Russian Federation, Spain, Indonesia, Hungary, South Africa, Germany, Mexico, Argentina, Singapore, Saudi Arabia, Colombia, Czech Republic, Canada, France, Croatia,Thailand, Bulgaria, Slovenia, Hong Kong, Poland, Sri Lanka, Chile, Japan, Austria, Ukraine, Azerbaijan, Ireland, Tunisia, Greece, Taiwan, Egypt, Bolivia, Paraguay, Iran, Islamic Republic , Morocco, Angola, Belgium, Portugal, Norway, Venezuela, United Arab Emirates, Algeria, Korea, Republic Of, Slovakia, Georgia, Lebanon, Macedonia, Sweden, Philippines, Vietnam, Dominican Republic