|
Frequently Asked Questions |
|
|
|
Frequently Asked Questions |
|
This page contains a list of Frequently Asked Questions for SQL Server Data Access Components.
If you have encounter a question with using SDAC, please browse through this list first. If this page does not answer your question, refer to the Getting Support topic in SDAC help.
Installation and Deployment
You may be having a compatibility issue that shows up in one or more of the following forms:
You can have such problems if you installed incompatible SDAC, ODAC, MyDAC or IBDAC versions. All these products use common base packages. The easiest way to avoid the problem is to uninstall all installed DAC products and then download from our site and install the last builds.
SDAC requires OLE DB installed on the workstation. In current versions of Microsoft Windows, such as Windows 2000, OLE DB is already included as part of the standard installation. But it is highly recommended to download the latest version (newer than 2.5) of Microsoft Data Access Components (MDAC).
Many features of SQL Server like Query Notifications, MARS require Microsoft SQL Server Native Client. If you need to use these features, you should download and install Microsoft SQL Server Native Client.
For applications that use SQL Server Compact Edition, the server itself is required to be installed on the client computer.
For more information, please refer to the Deployment topic of the SDAC help.
If you have purchased a full version of SDAC, you are entitled to distribute pre-compiled programs created with its use. You are not entitled to propagate any components inherited from SDAC or using SDAC source code. For more information see the License.rtf file in your SDAC installation directory.
You can create your own components that are inherited from SDAC or that use the SDAC source code. You are entitled to sell and distribute compiled application executables that use such components, but not their source code and not the components themselves.
The basic SDAC license agreement will remain the same. With SDAC 4.00, the SDAC Edition Matrix will be reorganized and a new SDAC Subscription Program will be introduced.
SDAC 4.00 will come in four editions: Trial, Standard, Professional, and Professional with Sources.
When you upgrade to the new version, your edition level will be automatically updated using the following Edition Correspondence Table.
Edition Correspondence Table for Upgrading to SDAC 4.00
| Old Edition Level | New Edition Level |
|---|---|
| - No Correspondence - | SDAC Standard Edition |
| SDAC Standard Edition | SDAC Professional Edition |
| SDAC Professional Edition | SDAC Professional Edition with Sources |
| SDAC Trial Edition | SDAC Trial Edition |
The feature list for each edition can be found in the SDAC documentation and on the SDAC website.
After SDAC 4.00, all upgrades to future versions are free to users with an active SDAC Subscription.
Users that have a registration for versions of SDAC prior to SDAC 4.00 will have to first upgrade to SDAC 4.00 to jump in on the Subscription program.
The SDAC Subscription Program is an annual maintenance and support service for SDAC users.
Users with a valid SDAC Subscription get the following benefits:
Priority Support is an advanced product support program which offers you expedited individual assistance with SDAC-related questions from the SDAC developers themselves. Priority Support is carried out over email and has a two business day response policy.
The SDAC Subscription Program is available for registered users of SDAC 4.00 and higher.
Yes, you can. SDAC version licenses are perpetual.
An annual SDAC Subscription is included when ordering or upgrading to any registered (non-Trial) edition of SDAC 4.00 or higher.
You can renew your SDAC Subscription on the SDAC Ordering Page. For more information, please contact [email protected].
To upgrade to SDAC 4.00, you can get a Version Update from the SDAC Ordering Page. For more information, please contact [email protected].
SDAC uses the lowest documented protocol level (OLE DB) to access the database server. This allows SDAC to achieve high performance. From time to time we compare SDAC with other products, and SDAC always takes first place.
Locate is performed on the client. So if you had set FetchAll to False when opening your dataset, cached only some of the rows on the client, and then invoked Locate, SDAC will have to fetch all the remaining rows from the server before performing the operation. On subsequent calls, Locate should work much faster.
If the Locate method keeps working slowly on subsequent calls or you are working with FetchAll=True, try the following. Perform local sorting by a field that is used in the Locate method. Just assign corresponding field name to the IndexFieldNames property.
To enable syntax highlighting for SDAC, you should download and install the freeware SynEdit component set.
You can determine your SDAC version number in several ways:
Just set the DBAccess.ChangeCursor variable to False anywhere in your program. The cursor will stop changing after this command is executed.
The values of these properties are templates for query statements, and they cannot be manually executed. Usually there is no need to fill these properties because the text of the query is generated automatically.
In special cases, you can set these properties to perform more complicated processing during a query. These properties are automatically processed by SDAC during the execution of the Post, Delete, or RefreshRecord methods, and are used to construct the query to the server. Their values can contain parameters with names of fields in the underlying data source, which will be later replaced by appropriate data values.
For example, you can use the SQLInsert template to insert a row into a query instance as follows.
The value of the SQLInsert property will then be used by SDAC to perform the last step.
Setting these properties is optional and allows you to automatically execute additional SQL statements, add calls to stored procedures and functions, check input parameters, and/or store comments during query execution. If these properties are not set, the SDAC dataset object will generate the query itself using the appropriate insert, update, delete, or refresh record syntax.
Use the TCustomDAConnection.GetDatabaseNames method.
The following questions usually arise from the same problem:
To fix this problem, you should add the SdacVcl unit to the uses clause of your project.
DbxSda is our dbExpress driver for SQL Server. dbExpress technology serves for providing a more or less uniform way to access different servers (SQL Server, MySQL, Oracle and so on). It is based on drivers that include server-specific features. Like any universal tool, in many specialized cases dbExpress providers lose some functionality. For example, the dbExpress design-time is quite poor and cannot be expanded.
SDAC is a specialized set of components for SQL Server, which has advanced server-specific design-time and a component interface similar to that of BDE.
We tried to include maximal support of SQL Server-specific features in both DbxSda and SDAC. However, the nature of dbExpress technology has some insurmountable restrictions. For example, Unicode fields cannot be passed from a driver to dbExpress.
SDAC and DbxSda use the same kernel and thus have similar performance. In some cases dbExpress is slower because data undergoes additional conversion to correspond to dbExpress standards.
To summarise, if it is important for you to be able to quickly adapt your application to a database server other than SQL Server, it is probably better to use DbxSda. In other cases, especially when migrating from BDE or ADO, you should use SDAC.
We always try to keep SDAC compatible with previous versions, but sometimes we have to change behaviour of SDAC in order to enhance its functionality, or avoid bugs. If either of changes is undesirable for your application, and you want to save the old behaviour, please refer to the "Compatibility with previous versions" topic in SDAC help. This topic describes such changes, and how to revert to the old SDAC behaviour.
Yes, SDAC is thread-safe but there is a restriction. But the same TCustomMSConnection object descendant cannot be used in several threads. So if you have a multithreaded application, you should have a TCustomMSConnection object descendant for each thread that uses SDAC.
This error occurs when the database server is unable to determine which record to modify or delete. In other words, there are either more than one record or no records that suit the UPDATE criteria. Such situation can happen when you omit the unique field in a SELECT statement (TCustomDADataSet.SQL) or when another user modifies the table simultaneously. This exception can be suppressed. Refer to TCustomDADataSet.Options topic in SDAC help for more information.
Usage of FetchAll=False mode has many advantages; however, it also has some restrictions since it requires an additional connection to server to be created for data fetching. The additional connection is created to prevent the main connection from blocking.
These problems can be avoided by setting the FetchAll property to True. Please see description of the FetchAll propery and the CreateConnection option in SDAC help for more information.
One more way to solve these problems is to use the Multiple Active Result Sets (MARS) feature. This feature lets you keep more than one unfetched record set within a single connection. To enable MARS, set the MultipleActiveResultSets option of TMSConnection to True. Note: To use MARS, you will need to have SQL Server and SQL Native Client installed.