Re: Bug with Multiple Result Sets?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

If you look at my posting from before, I already recoded my test program to
properly detect update counts as well as result sets. If DBCC is returning
update counts, then why do the JTurbo driver, the jTDS 1.0 driver, and the MS
2000 JDBC driver, when running the same commands against the same database,
not return them? I would need to define and execute a stored procedure
which actually does return an update count to demonstrate the other drivers
can handle update counts. The difference in behavior is not the 2005 SQL
Server engine, but the driver. Here are my results running your program with
all the drivers:

Class being loaded com.microsoft.sqlserver.jdbc.SQLServerDriver
URL being used:
jdbc:sqlserver://localhost:2005;selectMethod=direct;databaseName=AdventureWorks;user=sa;password=***

STAT_HEADER Results
Name: PK_Address_AddressID
Update count is: 1
DENSITY_VECTOR Results
Columns: AddressID
Update count is: 1
HISTOGRAM Results
RANGE_ROWS: 0
RANGE_ROWS: 1062
RANGE_ROWS: 95
RANGE_ROWS: 18431
RANGE_ROWS: 21
Update count is: 5
Update count is: 0

Class being loaded com.microsoft.jdbc.sqlserver.SQLServerDriver
URL being used:
jdbc:microsoft:sqlserver://localhost:2005;selectMethod=direct;databaseName=AdventureWorks;user=sa;password=***;

STAT_HEADER Results
Name: PK_Address_AddressID
DENSITY_VECTOR Results
Columns: AddressID
HISTOGRAM Results
RANGE_ROWS: 0
RANGE_ROWS: 1062
RANGE_ROWS: 95
RANGE_ROWS: 18431
RANGE_ROWS: 21

Class being loaded com.newatlanta.jturbo.driver.Driver
URL being used:
jdbc:JTurbo://localhost:2005/AdventureWorks/user=sa/password=***

STAT_HEADER Results
Name: PK_Address_AddressID
DENSITY_VECTOR Results
Columns: AddressID
HISTOGRAM Results
RANGE_ROWS: 0
RANGE_ROWS: 1062
RANGE_ROWS: 95
RANGE_ROWS: 18431
RANGE_ROWS: 21
Update count is: 0

Class being loaded net.sourceforge.jtds.jdbc.Driver
URL being used:
jdbc:jtds:sqlserver://localhost:2005/AdventureWorks;user=sa;password=***

STAT_HEADER Results
Name: PK_Address_AddressID
DENSITY_VECTOR Results
Columns: AddressID
HISTOGRAM Results
RANGE_ROWS: 0
RANGE_ROWS: 1062
RANGE_ROWS: 95
RANGE_ROWS: 18431
RANGE_ROWS: 21

Notice there are no update counts reported from the other drivers.

"Evan T. Basalik (MSFT)" wrote:

I just got some feedback from DEV and it looks like this is not a bug. Instead, what you are seeing is by-design. The problem is that dbcc returns an update
count after each result set. Therefore, when you check getMoreResults, it properly shows false b/c the next item is an update count, not a result set.
.

Relevant Pages

  • Re: Communication Driver Hooks
    ... Windows Driver Developer/Service ... "Christopher Lansing" wrote in message ... > COM port while my hook is installed. ... > the hook is properly installed, and that the test program works. ...
    (microsoft.public.development.device.drivers)
  • Re: RT : 2.6.12rc5 + realtime-preempt-2.6.12-rc5-V0.7.47-15
    ... > I have a test program which made a loop in RT to mesure the system ... The "via" driver had this problem until I identified ... For details search the unichrome-devel archives for "losing interrupts". ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Message signing fails when used in a driver
    ... then serialized and then imported into a certificate ... driver code. ... The reason for this is that the 'My' store of the system ... verify data) from a test program that completely runs in current ...
    (microsoft.public.platformsdk.security)
  • RE: :ODBC make test fails
    ... now you need to test with iODBC's test program. ... > not be sure until you test iODBC first. ... this looks like a unixodbc type of driver manager. ...
    (perl.dbi.users)
  • Re: 4990 C41 Scanning Issues
    ... >I started with Epson's driver, ... >Bottom line, the final scan looked nothing like the preview, ... would certainly not be consistent with the final scan. ... In order to judge the image by the histogram you need the histogram at ...
    (comp.periphs.scanners)