ni***********@gmail.com wrote:
I want to know the exact difference between collection ID and
qualifier.
In which context do you have "collection IDs"? I know that "qualifiers" are
used in replication scenarios. But maybe you have it somewhere else as
well?
I also want to know in detail : When we perform BIND operation on a
stored procedure, what we are actually trying to do ?
Why Bind operation is performed ??
When you create a bind file, the SQL statements in the embedded SQL code are
send to the database server (DB2 server), analyzed syntactically and
semantically, privileges are verified and then the statements are compiled
and optimized. As a final step the compiled statements are stored in the
bind file.
The binding itself takes the statements from those files and creates a
package in the database (can be another database than the one used for the
creation of the bind file). The existence of the tables (base tables or
views) is verified along with the privileges of the caller.
Can anyone please tell me bout complete Lifecycle of developing a
Stored Prcedure ??
I know following things : [I m using db2 Ver -8 ]
1) We create stored proc using developement center.
2) We perform build operation.
3) Later we Perform BIND operation.
4) We GRANT priveliges to other users for Ececution of stored proc in
case required.
5) You drop the procedure or database. ;-)
Seriously, the BIND operation is only necessary if you have SQL statements
embedded in C/C++ code. Java procedures or procedures written in SQL don't
require the bind files. Java procedures always use dynamic SQL and there
the SQL statements are send to the server and compiled/optimized there when
needed. And SQL procedures are directly translated into the DB2 internal
representation (called "section") when they are created (assuming you're on
V8.2).
--
Knut Stolze
DB2 Information Integration Development
IBM Germany
