Re: SQL Server connectivity

From: Doug Stoltz (NoSpam_at_MyEmail.com)
Date: 08/03/04


Date: Tue, 3 Aug 2004 17:59:42 -0400

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: Strange Problems with ODBC connection to SQL Server
    ... When accessing Jet data, use DAO. ... This way you are not exposing connection information in clear ... >accesses an SQL Server 2000 repository via ODBC data source. ...
    (microsoft.public.data.odbc)
  • Re: Access and processor usage
    ... and you are using an ODBC connection, that would be your bottle neck. ... bottleneck - need to step up to Sql Server. ...
    (comp.databases.ms-access)
  • 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: [ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send()) er
    ... I understand that you encountered the ODBC error message on your ecommerce ... TCP/IP protocol to your SQL Server instance by calling conn.Open, ... SQL Server instance and see if there is a connection reset when this issue ... Microsoft Online Community Support ...
    (microsoft.public.sqlserver.connect)
  • Re: Fujitsu cobol and SQLServer
    ... "Steve Rainbird" wrote in ... Server side cursors with SQL Server are not a good idea and are best avoided. ... Fujitsu assumes last connection until/unless you use SET CONNECTION. ... With microfocus cobol I never had this problem (true it is 4 or 5 yesrs since I used Mf and SQL server I tend to use Oracle). ...
    (comp.lang.cobol)