RE: SQL Server SP3a via JDBC SP2

From: Carb Simien [MSFT] (CarbinoS_at_online.microsoft.com)
Date: 09/16/04 

Date: Thu, 16 Sep 2004 21:35:19 GMT

--------------------
| Content-Class: urn:content-classes:message
| From: "Anna" <anonymous@discussions.microsoft.com>
| Sender: "Anna" <anonymous@discussions.microsoft.com>
| Subject: SQL Server SP3a via JDBC SP2
| Date: Wed, 1 Sep 2004 20:53:59 -0700
| Lines: 8
| Message-ID: <483c01c490a0$7a33f8d0$a501280a@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| thread-index: AcSQoHozPTxwM606QkGX0zwV3qKyXQ==
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| Path: cpmsftngxa10.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.jdbcdriver:6298
| NNTP-Posting-Host: tk2msftngxa13.phx.gbl 10.40.1.165
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| I have a java program that run on SQL Server 8.00.760 and
| original JDBC drive is no problem, but after apply the SQL
| Server SP3a 8.00.818, when execute a long sql script will
| got error (Invalid buffer received from client.. Error:
| 17805). Then I apply JDBC SP2, the script can run
| successfully, but the overall the sql script is execute
| very slow.
| Anyone to face the same problem?
|

The original issue regarding an invalid buffer is a client issue, and so it
is good to hear that the updated JDBC driver resolved the issue. However,
your latest question sounds more like a database performance issue. By
updating your SQL Server build, it is likely that your query execution plan
could have changed. Ensure that your indexes and statistics are up to
date. Then you should use SQL Profiler to see what type of query execution
plan is produced from one of the slow queries. The plan will tell you if
indexes are being used and which portion of the plan is the most expensive.

Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data

Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS
    ... I'm not seeing performance issues with the full enchilada installed, and 25 users busy hitting SQL. ... WSUS isn't difficult to uninstall - if you have WSUS v2 (installed with SBS R2) uninstall R2 from add/remove programs. ... How can anyone work with 4 instances of SQL Server on the same box? ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Resets
    ... If it were SQL that was falling short, ... The default backlog for SQL Server is 5. ... System.InvalidOperationException: Internal connection fatal error. ... From time to time, under heavy loads, we are getting resets at ...
    (microsoft.public.sqlserver.connect)
Loading