The AutoBind option forces SQL packages to be bound at connect time.
Normally the use of AutoBind is not recommended. Because this option always causes binding, AutoBind can adversely affect connect time performance.
The AutoBind option settings are defined in the table below:
|
Value |
Definition |
|
0 |
No auto-bind at connect time. The driver still binds packages dynamically if it does not find them on the server when it needs them. |
|
1 |
Binds packages at connect time, but uses NO REPLACE option on bind. If the packages already exist they will not be replaced. In the current version of StarSQL, AutoBind=1 ignores the NO REPLACE option and functions in the same manner as AutoBind=2. |
|
2 |
Binds packages at connect time and always replaces current packages, if there are any. |
|
N |
Same as 0. |
|
Y |
Same as 2. |
The packages that may be bound by 1 and 2 are:
the dynamic package for the current transaction isolation level
the catalog package
Regardless of the AutoBind setting, if the driver does not find packages on the host at the time they are needed, it will bind them dynamically.