Posted by joshsackett on 11/03/60 11:34

Here is an obscure question that I am sure can be dealt with from a
10,000 ft view:

I have installed Fuego (an enterprise level BPM). Another application
was built in-house to connect to Fuego (Fuego has two SQL 2000
databases to handle the business process flow and instance flow). This
in-house application then uses Tomcat & JDBC to connect to the above
mentioned Fuego databases and a third SQL 2000 database that handles
the actual data.

The entire gist is this: The application(s) run the SQL calls as a
standard

It is SQL Server performing all of the cursor work; I'm guessing
through whatever translation layer. Maybe JDBC is causing this? Has
anyone seen this before?

My second problem is that I let the application run for 1 day in user
acceptance testing and I ended up with 1.8GB procedure cache (all
cursors) at 50% cache hit ratio and 140MB of data cache at 99% cache
hit ratio. What could be the cause?

Thanks,
Josh

• Next in forum: Re: Deadlocks and Parallel Query Processing
• Prev in forum: Re: Indexes being improperly used when selecting data through a view
• Thread view: Fuego, Tomcat, JDBC & SQL Server 2000

[Reply to this message]