Re: Trying to decide whether to support DB2 or Oracle

On Mon, 07 May 2001 19:55:36 GMT, The Nomad wrote:
> > > 1) DB2 requires a C/C++ compiler to be installed on the database server
 for
> > > SQL stored procedures. What they seem to do is take your SQL stored
> > > procedure code, pass it through a pre-processor which generates C code,
 and
> > > from that they compile it into a .DLL which is then linked into the
> > > database. Absolutely absurd for deployability. I guess they want our
> > > documentation to read "to install our product, please install a C
 compiler
> > > on your database server and configure DB2 to know where to find it.
 Then,
> > > you can install our product."
> >
> > This will be (or already is) addressed. The requirement for the compiler
> > goes away (or already is).
> >
> > Ok, that doesn't help you anymore but maybe others...
>
> What do you mean "or already is"? Is it available? When will it be
> available?

That depends on which FixPack it will be in. I am not 100% familiar with all the details of the various FP's. That's why I'm rather careful with things outside the product I'm directly working on.

In another post today, Blair mentioned that this is already in FP3.

> I've got DB2 UDB 7.1 FP3, and it's still churning out .C files and compiling
> them into DLL's. For what it's worth, I've got 49 stored procedures - that's
> a lot of DLLs that get compiled by DB2/MS VC++ into DLLs to link into the
> database. If this is already addressed, tell me how to get it/activate
> it/install it. Please!

You should have the commands "GET ROUTINE" and "PUT ROUTINE". That way, you compile the STPs once on your build machine (A), run GET ROUTINE, copy the file created there to the machines (B) you want to install the STPs on, run PUT ROUTINE ON B and you're all set. No need for a C compiler on B.

-- 
Knut Stolze
DB2 UDB Spatial Extender
IBM Silicon Valley Lab