Help with Sort ID differences

Hi. I was wondering what is the default differences in the following 2 sort
order ids:
51 - SQL_Latin1_General_CP1_CS_AS collation.
71 - Latin1_General_CS_AS collation.
As some of you may have guess, the same SQL code returns different results
sets from two servers that are nearly the same with the execption being, the
Server's Sort ID.
Thanks,
JoeJoe,
The sort order will be differant for unicode data as well as ordinary string
data as windows and sql collations are slightly differant. Microsoft
describe the sql_ collations nicely in this article
http://support.microsoft.com/?id=322112.
This also points you to some examples of where the sort orders differ
e.g. a-c and ab
where the - is sorted differantly between the two collations
Chris
"Joe D" wrote:
> Hi. I was wondering what is the default differences in the following 2 sort
> order ids:
> 51 - SQL_Latin1_General_CP1_CS_AS collation.
> 71 - Latin1_General_CS_AS collation.
> As some of you may have guess, the same SQL code returns different results
> sets from two servers that are nearly the same with the execption being, the
> Server's Sort ID.
> Thanks,
> Joe
>
>|||Hi Chris,
Thanks for the pointer. I'll check it out.
Joe
"Chris Hoare" <choare@.nospam.nospam> wrote in message
news:2A1473C4-760B-4D2A-8421-1739AF812F45@.microsoft.com...
> Joe,
> The sort order will be differant for unicode data as well as ordinary
> string
> data as windows and sql collations are slightly differant. Microsoft
> describe the sql_ collations nicely in this article
> http://support.microsoft.com/?id=322112.
> This also points you to some examples of where the sort orders differ
> e.g. a-c and ab
> where the - is sorted differantly between the two collations
> Chris
> "Joe D" wrote:
>> Hi. I was wondering what is the default differences in the following 2
>> sort
>> order ids:
>> 51 - SQL_Latin1_General_CP1_CS_AS collation.
>> 71 - Latin1_General_CS_AS collation.
>> As some of you may have guess, the same SQL code returns different
>> results
>> sets from two servers that are nearly the same with the execption being,
>> the
>> Server's Sort ID.
>> Thanks,
>> Joe
>>

Help with Sort ID differences

Hi. I was wondering what is the default differences in the following 2 sort
order ids:
51 - SQL_Latin1_General_CP1_CS_AS collation.
71 - Latin1_General_CS_AS collation.
As some of you may have guess, the same SQL code returns different results
sets from two servers that are nearly the same with the execption being, the
Server's Sort ID.
Thanks,
JoeJoe,
The sort order will be differant for unicode data as well as ordinary string
data as windows and sql collations are slightly differant. Microsoft
describe the sql_ collations nicely in this article
http://support.microsoft.com/?id=322112.
This also points you to some examples of where the sort orders differ
e.g. a-c and ab
where the - is sorted differantly between the two collations
Chris
"Joe D" wrote:

> Hi. I was wondering what is the default differences in the following 2 sor
t
> order ids:
> 51 - SQL_Latin1_General_CP1_CS_AS collation.
> 71 - Latin1_General_CS_AS collation.
> As some of you may have guess, the same SQL code returns different result
s
> sets from two servers that are nearly the same with the execption being, t
he
> Server's Sort ID.
> Thanks,
> Joe
>
>|||Hi Chris,
Thanks for the pointer. I'll check it out.
Joe
"Chris Hoare" <choare@.nospam.nospam> wrote in message
news:2A1473C4-760B-4D2A-8421-1739AF812F45@.microsoft.com...[vbcol=seagreen]
> Joe,
> The sort order will be differant for unicode data as well as ordinary
> string
> data as windows and sql collations are slightly differant. Microsoft
> describe the sql_ collations nicely in this article
> http://support.microsoft.com/?id=322112.
> This also points you to some examples of where the sort orders differ
> e.g. a-c and ab
> where the - is sorted differantly between the two collations
> Chris
> "Joe D" wrote:
>sql

Help with JDBC Driver

Hello all,

I have a question about the SQL Server JDBC driver. I was wondering if
anyone knows what the default prefetch size is (in number of rows).
Also, does anyone know if an entire packet is sent (i.e. padded with
null values) if there is not enough data to fill it?

Thanks for your help!

tyTy,

The default fetch size with the MS driver is 1 in cursor mode and
"cache everything" in direct mode. These are basically the worst
choices possible: in cursor mode a fetch size of 1 will cause a request
to be made for each retrieved row and in direct mode there is normally
no need to cache the results to memory, they can be read on an "as
needed" basis.

With jTDS (of which I'm a developer) the default fetch size is of 100
rows for server side cursor based ResultSets (i.e.
scrollable/updateable) and no prefetching is done for direct executions
(i.e. fire hose cursors).

Please note that with both drivers you can set the fetch size you want
instead of the default.

Alin,
The jTDS Project.|||Hi Alin,

Thanks for the information!

ty

In article <1113635743.295152.122440@.z14g2000cwz.googlegroups. com>,
Alin Sinpalean <alin@.earthling.net> wrote:

> Ty,
> The default fetch size with the MS driver is 1 in cursor mode and
> "cache everything" in direct mode. These are basically the worst
> choices possible: in cursor mode a fetch size of 1 will cause a request
> to be made for each retrieved row and in direct mode there is normally
> no need to cache the results to memory, they can be read on an "as
> needed" basis.
> With jTDS (of which I'm a developer) the default fetch size is of 100
> rows for server side cursor based ResultSets (i.e.
> scrollable/updateable) and no prefetching is done for direct executions
> (i.e. fire hose cursors).
> Please note that with both drivers you can set the fetch size you want
> instead of the default.
> Alin,
> The jTDS Project.