Re: SQL Server connectivity

From: Alan (Alan_at_discussions.microsoft.com)
Date: 08/04/04 

Date: Wed, 4 Aug 2004 06:49:01 -0700

It has been always my practice to set the recordset cursor to client side.
I'll play with that a little bit a let you know what I can come up with.

"Doug Stoltz" wrote:

> Alan, I'd like to track the progress of your error. I've had similar issues
> resolved unsuccessfully. However, I think I may have clue for you.
>
> I feel like it must be something with the location of the cursors. Since
> obviously network bandwidth is not the problem.
>
> I suspect that you are using SERVER side cursors and your application has to
> make round trips over the VPN tunnel to fetch each row. The ODBC/Attached
> table connection is probably using CLIENT side cursors. (I think this is
> required by ODBC framework). Look at the cursor location setting and set
> for client side cursors and see if this helps. (At least it's something you
> can try.)
>
> Also, try running SQL profiler and see if this shows anything.
>
> Keep me updated - Doug
>
> "Alan" <Alan@discussions.microsoft.com> wrote in message
> news:C61B0D08-D236-481E-B1D7-CB511DD6B9F9@microsoft.com...
> > Hi,
> > I am using ADO connection to a SQL Server ODBC to run a custom
> application.
> > The problem is that the SQL server was moved to another office and a VPN
> tunnel was established to maintain connectibility.
> > Now, when the application is run, it performs 15-20 times slower.
> > I've tried many things and the only approach that solves this issue is
> creating an access database and linking the tables through the same ODBC.
> > I changed the connection to point to the odbc of the access database and
> the application is flying. Even faster then when it was ran locally.
> > Please help me identify what is the issue with the initial set up. I
> wouldn't like to use the rigged setup I stumblled upon/
> > Thanks
>
>
>

Relevant Pages

  • Re: SQL Server connectivity
    ... I feel like it must be something with the location of the cursors. ... table connection is probably using CLIENT side cursors. ... required by ODBC framework). ... > The problem is that the SQL server was moved to another office and a VPN ...
    (microsoft.public.data.ado)
  • Re: Fujitsu cobol and SQLServer
    ... I think from googling that I need to tell the odbc driver to use server ... Server side cursors with SQL Server are not a good idea and are best ... Fujitsu assumes last connection until/unless you use SET CONNECTION. ...
    (comp.lang.cobol)
  • Re: insert statement blocked
    ... I need uniqueidentifiers because my app is a three-tier client-server ... The client app may generate several records from different tables ... I have discovered that the SP heavily uses CURSORS:(( ...
    (comp.databases.ms-sqlserver)
  • Re: Database access sucks!
    ... In VB6 DAO recordsets the default was client ... side cursors, when ADO was introduced the default was server side cursors. ... Other database access methods don't allow this goofy design, ...
    (microsoft.public.dotnet.general)
  • Re: performace issue with a stored procedure
    ... the connection. ... Look for the high CPU command in the ... >>big difference between ODBC versus OLEDB connections ... >(ODBC tends to use cursors when it isn't ...
    (microsoft.public.sqlserver.programming)