We are using MS SQL 2000 and Cocoon 2 very sucessful in two big
projects.
We bought a JDBC Driver (SPRINTA and OPTA) from inet-software
(http://www.inetsoftware.de).
They are not cheap, but worth the money.

Stefan

> -----Original Message-----
> From: Horst Rutter [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, April 06, 2002 12:15 AM
> To: [EMAIL PROTECTED]; Nicola Ken Barozzi
> Subject: Re: Load test with ab
> 
> 
> Frustrating, I also have to communicate with a MS SQL 2000 db server.
> Not having started on the JDBC work I would be interested to know:
> a) what kind of experiences people have made using JDBC in a 
> Cocoon 2.x
> environment talking to MS SQL 2000
> b) any pointers to alternative (other than MS) JDBC drivers, 
> if that's the
> bottleneck.
> 
> Thanks,
> Horst
> 
> ----- Original Message -----
> From: "Nicola Ken Barozzi" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, April 04, 2002 11:57 PM
> Subject: Re: Load test with ab
> > "
> > Out of all the drivers we used, Microsoft's new JDBC driver 
> had the most
> > problems. It's still a beta driver in the form distributed 
> on Microsoft's
> > Web site, but it's not a new product per se, because it's 
> based on code
> > licensed from DataDirect Technologies Inc., which has had 
> the leading
> > third-party SQL Server JDBC driver for some years now.
> > Providing and supporting its own JDBC driver is a very 
> welcome move, and
> > Microsoft officials informed us last month that they had 
> 70,000 downloads
> of
> > the driver so far, so there is considerable customer interest in it.
> > However, the driver, in both Beta 1 and Beta 2 forms (we 
> tested both), has
> > serious performance and stability problems.
> > Using the driver, we were unable to get more than about
> 200-page-per-second
> > throughput, and the problem was clearly the driver-the 
> database was only
> at
> > about 15 percent to 20 percent CPU utilization at this 
> load. The driver
> also
> > has memory leaks: We could see on WebLogic's administration 
> console that
> > less memory was freed each time the Java virtual machine 
> did a garbage
> > collection. Because of these leaks, the Microsoft JDBC 
> driver was unable
> to
> > run for 8 hours straight.
> > "
> >
> > You should change driver (see 3rd party) od DB ;-)
> >
> > --
> > Nicola Ken Barozzi                   [EMAIL PROTECTED]
> >             - verba volant, scripta manent -
> >    (discussions get forgotten, just code remains)
> > 
> ---------------------------------------------------------------------
> >
> >
> > 
> ---------------------------------------------------------------------
> > Please check that your question has not already been answered in the
> > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> >
> > To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> > For additional commands, e-mail: <[EMAIL PROTECTED]>
> >
> >
> 
> 
> 
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> 
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
> 
> 
> 
> 
> 

---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

Reply via email to