Hi,
Hope this is neither too obvious or laughably impossible, else I'll
just have to be embarrased.
Is there any way to do this:
SELECT field1 if it is not NULL, else SELECT field2..??
The way this dbase is set up, I'm just about suicidal.
THANKS for any help!Use the COALESCE function (or NVL if using Oracle):
COALESCE(field1,field2)|||Originally posted by andrewst
Use the COALESCE function (or NVL if using Oracle):
COALESCE(field1,field2)
NVL did it! THANKS SO MUCH! I'd looked at that earlier but
the sql book I have only shows literals as being valid 'convert-to'
values. Shoulda just tried it. Thanks again!!!!!sqlsql
Showing posts with label sort. Show all posts
Showing posts with label sort. Show all posts
Sunday, March 25, 2012
Wednesday, March 7, 2012
Column Sorting
I want to be able to allow a user of a report to sort the records returnedc in a table control based on the column heading they select.
ie say the report returns a list of properties as row headings then a list of cost categories as column headings with cost values as the data. I want the user to be able to click on a column heading say a cost castegory of 'Cleaning' i then want the report to order the properties by 'Cleaning Value'
Is that possoble?
cheers.... anyone...
Regards,
Geoff|||
CTP - Community Technology Preview. It's a post-Beta release of the new Reporting Services 2005 due out this year. More information at -> http://www.microsoft.com/sql/2005/productinfo/ctp.mspx
As far as i know, the interactive sort was not available previous to this version. I was using a previous beta release of the 2005 edition and it did not have this capability.
|||cheers for this i guess i will have to just wait!Sunday, February 19, 2012
column heading centered when sort enabled
SQL Server 2005
I have a report with 20+ columns. Normally the text in each colum
heading is aligned at the top of the column heading. The column
heading is three lines high - there is so much text in some of the
columns - it takes three rows to display all of the column heading
text.
Without any sorting enabled - the column heading text is aligned to
the top of the heading row.
For columns with sorting enabled - it appears that it centers the
text. So column headings that are only one row - they are centered in
the heading row - whereas columns that are not sorted align at the
top.
The vertical align property for the row containing column headings is
set to top
It looks bad and I know my customer will object and might rather
disable sorting.
Any ideas?
Thanks!I believe I know what you are talking about. What is happening is that when
sorting is enabled it has to add the sorting "arrow" icon to the headers
and therefore moves the text around in the column header. If you want the
header to not change size (if the size of the cell is growing when you do
this) then turn the "CanGrow" property to "False" and see if that helps.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> From: GoogleGroups@.BaldwinNC.com
> Newsgroups: microsoft.public.sqlserver.reportingsvcs
> Subject: column heading centered when sort enabled
> Date: Tue, 02 Oct 2007 07:03:15 -0700
> SQL Server 2005
> I have a report with 20+ columns. Normally the text in each colum
> heading is aligned at the top of the column heading. The column
> heading is three lines high - there is so much text in some of the
> columns - it takes three rows to display all of the column heading
> text.
> Without any sorting enabled - the column heading text is aligned to
> the top of the heading row.
> For columns with sorting enabled - it appears that it centers the
> text. So column headings that are only one row - they are centered in
> the heading row - whereas columns that are not sorted align at the
> top.
> The vertical align property for the row containing column headings is
> set to top
> It looks bad and I know my customer will object and might rather
> disable sorting.
> Any ideas?
> Thanks!
>|||Thanks for the idea. I only had to change the very first column,
TextBox properties, Format Tab, - I unchecked the "Can increase to
accomodate contents".
Note I only modified the first column heading textbox properties - and
all column headings now appear to be aligned (correctly) to the top.
Thanks!|||I take my last post back. When I "previewed" the report changing just
the first column seemed to fix all columns. But when I deploy the
report - I had to change each column.|||Great. Glad we got it working for you at least :)
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> From: GoogleGroups@.BaldwinNC.com
> Newsgroups: microsoft.public.sqlserver.reportingsvcs
> Subject: Re: column heading centered when sort enabled
> Date: Tue, 02 Oct 2007 10:37:17 -0700
> I take my last post back. When I "previewed" the report changing just
> the first column seemed to fix all columns. But when I deploy the
> report - I had to change each column.
>
I have a report with 20+ columns. Normally the text in each colum
heading is aligned at the top of the column heading. The column
heading is three lines high - there is so much text in some of the
columns - it takes three rows to display all of the column heading
text.
Without any sorting enabled - the column heading text is aligned to
the top of the heading row.
For columns with sorting enabled - it appears that it centers the
text. So column headings that are only one row - they are centered in
the heading row - whereas columns that are not sorted align at the
top.
The vertical align property for the row containing column headings is
set to top
It looks bad and I know my customer will object and might rather
disable sorting.
Any ideas?
Thanks!I believe I know what you are talking about. What is happening is that when
sorting is enabled it has to add the sorting "arrow" icon to the headers
and therefore moves the text around in the column header. If you want the
header to not change size (if the size of the cell is growing when you do
this) then turn the "CanGrow" property to "False" and see if that helps.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> From: GoogleGroups@.BaldwinNC.com
> Newsgroups: microsoft.public.sqlserver.reportingsvcs
> Subject: column heading centered when sort enabled
> Date: Tue, 02 Oct 2007 07:03:15 -0700
> SQL Server 2005
> I have a report with 20+ columns. Normally the text in each colum
> heading is aligned at the top of the column heading. The column
> heading is three lines high - there is so much text in some of the
> columns - it takes three rows to display all of the column heading
> text.
> Without any sorting enabled - the column heading text is aligned to
> the top of the heading row.
> For columns with sorting enabled - it appears that it centers the
> text. So column headings that are only one row - they are centered in
> the heading row - whereas columns that are not sorted align at the
> top.
> The vertical align property for the row containing column headings is
> set to top
> It looks bad and I know my customer will object and might rather
> disable sorting.
> Any ideas?
> Thanks!
>|||Thanks for the idea. I only had to change the very first column,
TextBox properties, Format Tab, - I unchecked the "Can increase to
accomodate contents".
Note I only modified the first column heading textbox properties - and
all column headings now appear to be aligned (correctly) to the top.
Thanks!|||I take my last post back. When I "previewed" the report changing just
the first column seemed to fix all columns. But when I deploy the
report - I had to change each column.|||Great. Glad we got it working for you at least :)
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> From: GoogleGroups@.BaldwinNC.com
> Newsgroups: microsoft.public.sqlserver.reportingsvcs
> Subject: Re: column heading centered when sort enabled
> Date: Tue, 02 Oct 2007 10:37:17 -0700
> I take my last post back. When I "previewed" the report changing just
> the first column seemed to fix all columns. But when I deploy the
> report - I had to change each column.
>
Column header properties gone after using URL report access
I set a border and interactive sort action properties to columns in a
report. When I render the report using a URL I lose those column header
properties. Is there a URL command to pass those settings with the URL?
(I'm using 'rs:Command=Render&rs:Format=HTML4.0' plus passing some
params)
For more description see my post at: Pagination question - retrieve
only records for each page
http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/024cb61912a7630e/4e5c08587fee845a#4e5c08587fee845a
FredMy mistake. I copied and pasted the url from the previous version and
didn't update the file name in the url. I was just calling the old
version when ever I hit my 'next' button. Everything is working now.
report. When I render the report using a URL I lose those column header
properties. Is there a URL command to pass those settings with the URL?
(I'm using 'rs:Command=Render&rs:Format=HTML4.0' plus passing some
params)
For more description see my post at: Pagination question - retrieve
only records for each page
http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/024cb61912a7630e/4e5c08587fee845a#4e5c08587fee845a
FredMy mistake. I copied and pasted the url from the previous version and
didn't update the file name in the url. I was just calling the old
version when ever I hit my 'next' button. Everything is working now.
Friday, February 10, 2012
Collation Properties
Hi,
I want to specify case sensitivity for my database, but at the same time i
want let customer decide the sort order.
What i mean is: take the following collation property
SQL_Latin1_general_cs_as
in the above property, i want to specify only CS, and let cusotmer decide
what to (example: what sort order) specify.
Is it possible? How to do this? I hope this is a very natural requirement,
but could find help in MS documents for this
Thanks,
Venkat
The collation determines the sort rules, so you cannot specify a Collation
and apply different sort rules.
Consider two other important issues:
- a collation applied to a single database involves problems regarding the
collation of the other databases of the same instance (eg. master, msdb, etc).
To resolve this issue is better apply a specific collation to the table
columns (very tedious but...).
the Latin1_general_cs_as sorts upper case and lower case separately but in a
different way among Latin1_General_BIN;I don't remember exactly which one,
but one sorts all the upper cases together separately among the lower case,
the other sorts instead A with a, B with b and so on.
Remeber furthermore tha the new collation does'nt convert the collation of
data already present in your tables.
"Venkat" wrote:
> Hi,
> I want to specify case sensitivity for my database, but at the same time i
> want let customer decide the sort order.
> What i mean is: take the following collation property
> SQL_Latin1_general_cs_as
> in the above property, i want to specify only CS, and let cusotmer decide
> what to (example: what sort order) specify.
> Is it possible? How to do this? I hope this is a very natural requirement,
> but could find help in MS documents for this
> Thanks,
> Venkat
>
>
|||Hi,
I would like to understand your statement:
" collation applied to a single database involves problems regarding the
collation of the other databases of the same instance (eg. master, msdb,
etc)."
What is the problem if my database is in diffrent collaiton than the master
database?
I am sure this is possible and there would be no issuees with this.
There might be issues with tempdb, so you can specify collation when you are
creating temp tables.
Can you tell me what is the problems you are expecting if master database
and user database is in diffrent collation?
Other thing you said is: sorting, case sensitivity, accent sensitivity (I
call them as collaiton properties) have to be specified together only?
the reason you said is: all these properties together forms as sort rules?
If so, then when the properties: Latin1, General going to be used and what
purpose they are for? (asume that i have Unicode database)
comments?
Regards,
Venkat
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...[vbcol=seagreen]
> The collation determines the sort rules, so you cannot specify a Collation
> and apply different sort rules.
> Consider two other important issues:
> - a collation applied to a single database involves problems regarding the
> collation of the other databases of the same instance (eg. master, msdb,
> etc).
> To resolve this issue is better apply a specific collation to the table
> columns (very tedious but...).
> the Latin1_general_cs_as sorts upper case and lower case separately but in
> a
> different way among Latin1_General_BIN;I don't remember exactly which one,
> but one sorts all the upper cases together separately among the lower
> case,
> the other sorts instead A with a, B with b and so on.
> Remeber furthermore tha the new collation does'nt convert the collation
> of
> data already present in your tables.
>
> "Venkat" wrote:
|||Hi,
i wrote about issues in generic terms: having objects in different
collations COULD be an issue, but not necessarily IS. Surely some (very
little) overhead due to internal conversion is more probable in presence of
more than one collation.
More: the sort order is implicit in the collation you select: BIN (binary)
sort is different among CS_AS or CI_AS or CI_AI etc.
So the Properties Latin1, General are "complementary" with the CS, CI, AS,
AI, KS (etc.) properties: the sort order could be different among each
available combination.
The concept of collation involves not only sort rules but also character set
consideration.
You cannot define o sort order apart from the selected collation.
"Venkat" wrote:
> Hi,
> I would like to understand your statement:
> " collation applied to a single database involves problems regarding the
> collation of the other databases of the same instance (eg. master, msdb,
> etc)."
> What is the problem if my database is in diffrent collaiton than the master
> database?
> I am sure this is possible and there would be no issuees with this.
> There might be issues with tempdb, so you can specify collation when you are
> creating temp tables.
> Can you tell me what is the problems you are expecting if master database
> and user database is in diffrent collation?
> Other thing you said is: sorting, case sensitivity, accent sensitivity (I
> call them as collaiton properties) have to be specified together only?
> the reason you said is: all these properties together forms as sort rules?
> If so, then when the properties: Latin1, General going to be used and what
> purpose they are for? (asume that i have Unicode database)
> comments?
> Regards,
> Venkat
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...
>
>
|||Hi,
I would like to restate what you said about "complimentary" properties like
Latin, General etc.,
As per my understanding these complimentary properties are useful for non
unicode database.
Beucase as per my guess these properties (Latin, General etc.,) specifies
how the data can be stored: in which character set for non unicode database.
Where as these complimnetary properties are of no use (but we still need to
specify) for unicode database.
You have any comments on my understanding?
Regards,
Venkat
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:BF5A2E30-5D28-4129-B025-487DB4F6949D@.microsoft.com...[vbcol=seagreen]
> Hi,
> i wrote about issues in generic terms: having objects in different
> collations COULD be an issue, but not necessarily IS. Surely some (very
> little) overhead due to internal conversion is more probable in presence
> of
> more than one collation.
> More: the sort order is implicit in the collation you select: BIN (binary)
> sort is different among CS_AS or CI_AS or CI_AI etc.
> So the Properties Latin1, General are "complementary" with the CS, CI, AS,
> AI, KS (etc.) properties: the sort order could be different among each
> available combination.
> The concept of collation involves not only sort rules but also character
> set
> consideration.
> You cannot define o sort order apart from the selected collation.
>
> "Venkat" wrote:
|||No comments about your understanding.
The question is:
Apart (in unicode evironment) from "localizations" given by the different
available collations (Latin, Japanese, etc), the sort rules are different
between CS, CI, AS, AI,or any combination of them you'll like to select and
the BIN option: anyway, you can make just one choice: so you will provide a
"binary" sort criteria or a case, accent and/or katana sensitivity (or
insensitivity) sorto criteria, depending on the collation you'll set for your
Server, database or column
Regards
Gilberto
"Venkat" wrote:
> Hi,
> I would like to restate what you said about "complimentary" properties like
> Latin, General etc.,
> As per my understanding these complimentary properties are useful for non
> unicode database.
> Beucase as per my guess these properties (Latin, General etc.,) specifies
> how the data can be stored: in which character set for non unicode database.
> Where as these complimnetary properties are of no use (but we still need to
> specify) for unicode database.
> You have any comments on my understanding?
> Regards,
> Venkat
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:BF5A2E30-5D28-4129-B025-487DB4F6949D@.microsoft.com...
>
>
I want to specify case sensitivity for my database, but at the same time i
want let customer decide the sort order.
What i mean is: take the following collation property
SQL_Latin1_general_cs_as
in the above property, i want to specify only CS, and let cusotmer decide
what to (example: what sort order) specify.
Is it possible? How to do this? I hope this is a very natural requirement,
but could find help in MS documents for this
Thanks,
Venkat
The collation determines the sort rules, so you cannot specify a Collation
and apply different sort rules.
Consider two other important issues:
- a collation applied to a single database involves problems regarding the
collation of the other databases of the same instance (eg. master, msdb, etc).
To resolve this issue is better apply a specific collation to the table
columns (very tedious but...).
the Latin1_general_cs_as sorts upper case and lower case separately but in a
different way among Latin1_General_BIN;I don't remember exactly which one,
but one sorts all the upper cases together separately among the lower case,
the other sorts instead A with a, B with b and so on.
Remeber furthermore tha the new collation does'nt convert the collation of
data already present in your tables.
"Venkat" wrote:
> Hi,
> I want to specify case sensitivity for my database, but at the same time i
> want let customer decide the sort order.
> What i mean is: take the following collation property
> SQL_Latin1_general_cs_as
> in the above property, i want to specify only CS, and let cusotmer decide
> what to (example: what sort order) specify.
> Is it possible? How to do this? I hope this is a very natural requirement,
> but could find help in MS documents for this
> Thanks,
> Venkat
>
>
|||Hi,
I would like to understand your statement:
" collation applied to a single database involves problems regarding the
collation of the other databases of the same instance (eg. master, msdb,
etc)."
What is the problem if my database is in diffrent collaiton than the master
database?
I am sure this is possible and there would be no issuees with this.
There might be issues with tempdb, so you can specify collation when you are
creating temp tables.
Can you tell me what is the problems you are expecting if master database
and user database is in diffrent collation?
Other thing you said is: sorting, case sensitivity, accent sensitivity (I
call them as collaiton properties) have to be specified together only?
the reason you said is: all these properties together forms as sort rules?
If so, then when the properties: Latin1, General going to be used and what
purpose they are for? (asume that i have Unicode database)
comments?
Regards,
Venkat
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...[vbcol=seagreen]
> The collation determines the sort rules, so you cannot specify a Collation
> and apply different sort rules.
> Consider two other important issues:
> - a collation applied to a single database involves problems regarding the
> collation of the other databases of the same instance (eg. master, msdb,
> etc).
> To resolve this issue is better apply a specific collation to the table
> columns (very tedious but...).
> the Latin1_general_cs_as sorts upper case and lower case separately but in
> a
> different way among Latin1_General_BIN;I don't remember exactly which one,
> but one sorts all the upper cases together separately among the lower
> case,
> the other sorts instead A with a, B with b and so on.
> Remeber furthermore tha the new collation does'nt convert the collation
> of
> data already present in your tables.
>
> "Venkat" wrote:
|||Hi,
i wrote about issues in generic terms: having objects in different
collations COULD be an issue, but not necessarily IS. Surely some (very
little) overhead due to internal conversion is more probable in presence of
more than one collation.
More: the sort order is implicit in the collation you select: BIN (binary)
sort is different among CS_AS or CI_AS or CI_AI etc.
So the Properties Latin1, General are "complementary" with the CS, CI, AS,
AI, KS (etc.) properties: the sort order could be different among each
available combination.
The concept of collation involves not only sort rules but also character set
consideration.
You cannot define o sort order apart from the selected collation.
"Venkat" wrote:
> Hi,
> I would like to understand your statement:
> " collation applied to a single database involves problems regarding the
> collation of the other databases of the same instance (eg. master, msdb,
> etc)."
> What is the problem if my database is in diffrent collaiton than the master
> database?
> I am sure this is possible and there would be no issuees with this.
> There might be issues with tempdb, so you can specify collation when you are
> creating temp tables.
> Can you tell me what is the problems you are expecting if master database
> and user database is in diffrent collation?
> Other thing you said is: sorting, case sensitivity, accent sensitivity (I
> call them as collaiton properties) have to be specified together only?
> the reason you said is: all these properties together forms as sort rules?
> If so, then when the properties: Latin1, General going to be used and what
> purpose they are for? (asume that i have Unicode database)
> comments?
> Regards,
> Venkat
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...
>
>
|||Hi,
I would like to restate what you said about "complimentary" properties like
Latin, General etc.,
As per my understanding these complimentary properties are useful for non
unicode database.
Beucase as per my guess these properties (Latin, General etc.,) specifies
how the data can be stored: in which character set for non unicode database.
Where as these complimnetary properties are of no use (but we still need to
specify) for unicode database.
You have any comments on my understanding?
Regards,
Venkat
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:BF5A2E30-5D28-4129-B025-487DB4F6949D@.microsoft.com...[vbcol=seagreen]
> Hi,
> i wrote about issues in generic terms: having objects in different
> collations COULD be an issue, but not necessarily IS. Surely some (very
> little) overhead due to internal conversion is more probable in presence
> of
> more than one collation.
> More: the sort order is implicit in the collation you select: BIN (binary)
> sort is different among CS_AS or CI_AS or CI_AI etc.
> So the Properties Latin1, General are "complementary" with the CS, CI, AS,
> AI, KS (etc.) properties: the sort order could be different among each
> available combination.
> The concept of collation involves not only sort rules but also character
> set
> consideration.
> You cannot define o sort order apart from the selected collation.
>
> "Venkat" wrote:
|||No comments about your understanding.
The question is:
Apart (in unicode evironment) from "localizations" given by the different
available collations (Latin, Japanese, etc), the sort rules are different
between CS, CI, AS, AI,or any combination of them you'll like to select and
the BIN option: anyway, you can make just one choice: so you will provide a
"binary" sort criteria or a case, accent and/or katana sensitivity (or
insensitivity) sorto criteria, depending on the collation you'll set for your
Server, database or column
Regards
Gilberto
"Venkat" wrote:
> Hi,
> I would like to restate what you said about "complimentary" properties like
> Latin, General etc.,
> As per my understanding these complimentary properties are useful for non
> unicode database.
> Beucase as per my guess these properties (Latin, General etc.,) specifies
> how the data can be stored: in which character set for non unicode database.
> Where as these complimnetary properties are of no use (but we still need to
> specify) for unicode database.
> You have any comments on my understanding?
> Regards,
> Venkat
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:BF5A2E30-5D28-4129-B025-487DB4F6949D@.microsoft.com...
>
>
Collation Properties
Hi,
I want to specify case sensitivity for my database, but at the same time i
want let customer decide the sort order.
What i mean is: take the following collation property
SQL_Latin1_general_cs_as
in the above property, i want to specify only CS, and let cusotmer decide
what to (example: what sort order) specify.
Is it possible? How to do this? I hope this is a very natural requirement,
but could find help in MS documents for this
Thanks,
VenkatThe collation determines the sort rules, so you cannot specify a Collation
and apply different sort rules.
Consider two other important issues:
- a collation applied to a single database involves problems regarding the
collation of the other databases of the same instance (eg. master, msdb, etc
).
To resolve this issue is better apply a specific collation to the table
columns (very tedious but...).
the Latin1_general_cs_as sorts upper case and lower case separately but in a
different way among Latin1_General_BIN;I don't remember exactly which one,
but one sorts all the upper cases together separately among the lower case,
the other sorts instead A with a, B with b and so on.
Remeber furthermore tha the new collation does'nt convert the collation of
data already present in your tables.
"Venkat" wrote:
> Hi,
> I want to specify case sensitivity for my database, but at the same time i
> want let customer decide the sort order.
> What i mean is: take the following collation property
> SQL_Latin1_general_cs_as
> in the above property, i want to specify only CS, and let cusotmer decide
> what to (example: what sort order) specify.
> Is it possible? How to do this? I hope this is a very natural requirement,
> but could find help in MS documents for this
> Thanks,
> Venkat
>
>|||Hi,
I would like to understand your statement:
" collation applied to a single database involves problems regarding the
collation of the other databases of the same instance (eg. master, msdb,
etc)."
What is the problem if my database is in diffrent collaiton than the master
database?
I am sure this is possible and there would be no issuees with this.
There might be issues with tempdb, so you can specify collation when you are
creating temp tables.
Can you tell me what is the problems you are expecting if master database
and user database is in diffrent collation?
Other thing you said is: sorting, case sensitivity, accent sensitivity (I
call them as collaiton properties) have to be specified together only?
the reason you said is: all these properties together forms as sort rules?
If so, then when the properties: Latin1, General going to be used and what
purpose they are for? (asume that i have Unicode database)
comments?
Regards,
Venkat
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...[vbcol=seagreen]
> The collation determines the sort rules, so you cannot specify a Collation
> and apply different sort rules.
> Consider two other important issues:
> - a collation applied to a single database involves problems regarding the
> collation of the other databases of the same instance (eg. master, msdb,
> etc).
> To resolve this issue is better apply a specific collation to the table
> columns (very tedious but...).
> the Latin1_general_cs_as sorts upper case and lower case separately but in
> a
> different way among Latin1_General_BIN;I don't remember exactly which one,
> but one sorts all the upper cases together separately among the lower
> case,
> the other sorts instead A with a, B with b and so on.
> Remeber furthermore tha the new collation does'nt convert the collation
> of
> data already present in your tables.
>
> "Venkat" wrote:
>|||Hi,
i wrote about issues in generic terms: having objects in different
collations COULD be an issue, but not necessarily IS. Surely some (very
little) overhead due to internal conversion is more probable in presence of
more than one collation.
More: the sort order is implicit in the collation you select: BIN (binary)
sort is different among CS_AS or CI_AS or CI_AI etc.
So the Properties Latin1, General are "complementary" with the CS, CI, AS,
AI, KS (etc.) properties: the sort order could be different among each
available combination.
The concept of collation involves not only sort rules but also character set
consideration.
You cannot define o sort order apart from the selected collation.
"Venkat" wrote:
> Hi,
> I would like to understand your statement:
> " collation applied to a single database involves problems regarding the
> collation of the other databases of the same instance (eg. master, msdb,
> etc)."
> What is the problem if my database is in diffrent collaiton than the maste
r
> database?
> I am sure this is possible and there would be no issuees with this.
> There might be issues with tempdb, so you can specify collation when you a
re
> creating temp tables.
> Can you tell me what is the problems you are expecting if master database
> and user database is in diffrent collation?
> Other thing you said is: sorting, case sensitivity, accent sensitivity (I
> call them as collaiton properties) have to be specified together only?
> the reason you said is: all these properties together forms as sort rules?
> If so, then when the properties: Latin1, General going to be used and what
> purpose they are for? (asume that i have Unicode database)
> comments?
> Regards,
> Venkat
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...
>
>|||Hi,
I would like to restate what you said about "complimentary" properties like
Latin, General etc.,
As per my understanding these complimentary properties are useful for non
unicode database.
Beucase as per my guess these properties (Latin, General etc.,) specifies
how the data can be stored: in which character set for non unicode database.
Where as these complimnetary properties are of no use (but we still need to
specify) for unicode database.
You have any comments on my understanding?
Regards,
Venkat
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:BF5A2E30-5D28-4129-B025-487DB4F6949D@.microsoft.com...[vbcol=seagreen]
> Hi,
> i wrote about issues in generic terms: having objects in different
> collations COULD be an issue, but not necessarily IS. Surely some (very
> little) overhead due to internal conversion is more probable in presence
> of
> more than one collation.
> More: the sort order is implicit in the collation you select: BIN (binary)
> sort is different among CS_AS or CI_AS or CI_AI etc.
> So the Properties Latin1, General are "complementary" with the CS, CI, AS,
> AI, KS (etc.) properties: the sort order could be different among each
> available combination.
> The concept of collation involves not only sort rules but also character
> set
> consideration.
> You cannot define o sort order apart from the selected collation.
>
> "Venkat" wrote:
>|||No comments about your understanding.
The question is:
Apart (in unicode evironment) from "localizations" given by the different
available collations (Latin, Japanese, etc), the sort rules are different
between CS, CI, AS, AI,or any combination of them you'll like to select and
the BIN option: anyway, you can make just one choice: so you will provide a
"binary" sort criteria or a case, accent and/or katana sensitivity (or
insensitivity) sorto criteria, depending on the collation you'll set for you
r
Server, database or column
Regards
Gilberto
"Venkat" wrote:
> Hi,
> I would like to restate what you said about "complimentary" properties lik
e
> Latin, General etc.,
> As per my understanding these complimentary properties are useful for non
> unicode database.
> Beucase as per my guess these properties (Latin, General etc.,) specifies
> how the data can be stored: in which character set for non unicode databas
e.
> Where as these complimnetary properties are of no use (but we still need t
o
> specify) for unicode database.
> You have any comments on my understanding?
> Regards,
> Venkat
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:BF5A2E30-5D28-4129-B025-487DB4F6949D@.microsoft.com...
>
>
I want to specify case sensitivity for my database, but at the same time i
want let customer decide the sort order.
What i mean is: take the following collation property
SQL_Latin1_general_cs_as
in the above property, i want to specify only CS, and let cusotmer decide
what to (example: what sort order) specify.
Is it possible? How to do this? I hope this is a very natural requirement,
but could find help in MS documents for this
Thanks,
VenkatThe collation determines the sort rules, so you cannot specify a Collation
and apply different sort rules.
Consider two other important issues:
- a collation applied to a single database involves problems regarding the
collation of the other databases of the same instance (eg. master, msdb, etc
).
To resolve this issue is better apply a specific collation to the table
columns (very tedious but...).
the Latin1_general_cs_as sorts upper case and lower case separately but in a
different way among Latin1_General_BIN;I don't remember exactly which one,
but one sorts all the upper cases together separately among the lower case,
the other sorts instead A with a, B with b and so on.
Remeber furthermore tha the new collation does'nt convert the collation of
data already present in your tables.
"Venkat" wrote:
> Hi,
> I want to specify case sensitivity for my database, but at the same time i
> want let customer decide the sort order.
> What i mean is: take the following collation property
> SQL_Latin1_general_cs_as
> in the above property, i want to specify only CS, and let cusotmer decide
> what to (example: what sort order) specify.
> Is it possible? How to do this? I hope this is a very natural requirement,
> but could find help in MS documents for this
> Thanks,
> Venkat
>
>|||Hi,
I would like to understand your statement:
" collation applied to a single database involves problems regarding the
collation of the other databases of the same instance (eg. master, msdb,
etc)."
What is the problem if my database is in diffrent collaiton than the master
database?
I am sure this is possible and there would be no issuees with this.
There might be issues with tempdb, so you can specify collation when you are
creating temp tables.
Can you tell me what is the problems you are expecting if master database
and user database is in diffrent collation?
Other thing you said is: sorting, case sensitivity, accent sensitivity (I
call them as collaiton properties) have to be specified together only?
the reason you said is: all these properties together forms as sort rules?
If so, then when the properties: Latin1, General going to be used and what
purpose they are for? (asume that i have Unicode database)
comments?
Regards,
Venkat
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...[vbcol=seagreen]
> The collation determines the sort rules, so you cannot specify a Collation
> and apply different sort rules.
> Consider two other important issues:
> - a collation applied to a single database involves problems regarding the
> collation of the other databases of the same instance (eg. master, msdb,
> etc).
> To resolve this issue is better apply a specific collation to the table
> columns (very tedious but...).
> the Latin1_general_cs_as sorts upper case and lower case separately but in
> a
> different way among Latin1_General_BIN;I don't remember exactly which one,
> but one sorts all the upper cases together separately among the lower
> case,
> the other sorts instead A with a, B with b and so on.
> Remeber furthermore tha the new collation does'nt convert the collation
> of
> data already present in your tables.
>
> "Venkat" wrote:
>|||Hi,
i wrote about issues in generic terms: having objects in different
collations COULD be an issue, but not necessarily IS. Surely some (very
little) overhead due to internal conversion is more probable in presence of
more than one collation.
More: the sort order is implicit in the collation you select: BIN (binary)
sort is different among CS_AS or CI_AS or CI_AI etc.
So the Properties Latin1, General are "complementary" with the CS, CI, AS,
AI, KS (etc.) properties: the sort order could be different among each
available combination.
The concept of collation involves not only sort rules but also character set
consideration.
You cannot define o sort order apart from the selected collation.
"Venkat" wrote:
> Hi,
> I would like to understand your statement:
> " collation applied to a single database involves problems regarding the
> collation of the other databases of the same instance (eg. master, msdb,
> etc)."
> What is the problem if my database is in diffrent collaiton than the maste
r
> database?
> I am sure this is possible and there would be no issuees with this.
> There might be issues with tempdb, so you can specify collation when you a
re
> creating temp tables.
> Can you tell me what is the problems you are expecting if master database
> and user database is in diffrent collation?
> Other thing you said is: sorting, case sensitivity, accent sensitivity (I
> call them as collaiton properties) have to be specified together only?
> the reason you said is: all these properties together forms as sort rules?
> If so, then when the properties: Latin1, General going to be used and what
> purpose they are for? (asume that i have Unicode database)
> comments?
> Regards,
> Venkat
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...
>
>|||Hi,
I would like to restate what you said about "complimentary" properties like
Latin, General etc.,
As per my understanding these complimentary properties are useful for non
unicode database.
Beucase as per my guess these properties (Latin, General etc.,) specifies
how the data can be stored: in which character set for non unicode database.
Where as these complimnetary properties are of no use (but we still need to
specify) for unicode database.
You have any comments on my understanding?
Regards,
Venkat
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:BF5A2E30-5D28-4129-B025-487DB4F6949D@.microsoft.com...[vbcol=seagreen]
> Hi,
> i wrote about issues in generic terms: having objects in different
> collations COULD be an issue, but not necessarily IS. Surely some (very
> little) overhead due to internal conversion is more probable in presence
> of
> more than one collation.
> More: the sort order is implicit in the collation you select: BIN (binary)
> sort is different among CS_AS or CI_AS or CI_AI etc.
> So the Properties Latin1, General are "complementary" with the CS, CI, AS,
> AI, KS (etc.) properties: the sort order could be different among each
> available combination.
> The concept of collation involves not only sort rules but also character
> set
> consideration.
> You cannot define o sort order apart from the selected collation.
>
> "Venkat" wrote:
>|||No comments about your understanding.
The question is:
Apart (in unicode evironment) from "localizations" given by the different
available collations (Latin, Japanese, etc), the sort rules are different
between CS, CI, AS, AI,or any combination of them you'll like to select and
the BIN option: anyway, you can make just one choice: so you will provide a
"binary" sort criteria or a case, accent and/or katana sensitivity (or
insensitivity) sorto criteria, depending on the collation you'll set for you
r
Server, database or column
Regards
Gilberto
"Venkat" wrote:
> Hi,
> I would like to restate what you said about "complimentary" properties lik
e
> Latin, General etc.,
> As per my understanding these complimentary properties are useful for non
> unicode database.
> Beucase as per my guess these properties (Latin, General etc.,) specifies
> how the data can be stored: in which character set for non unicode databas
e.
> Where as these complimnetary properties are of no use (but we still need t
o
> specify) for unicode database.
> You have any comments on my understanding?
> Regards,
> Venkat
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:BF5A2E30-5D28-4129-B025-487DB4F6949D@.microsoft.com...
>
>
Collation Properties
Hi,
I want to specify case sensitivity for my database, but at the same time i
want let customer decide the sort order.
What i mean is: take the following collation property
SQL_Latin1_general_cs_as
in the above property, i want to specify only CS, and let cusotmer decide
what to (example: what sort order) specify.
Is it possible? How to do this? I hope this is a very natural requirement,
but could find help in MS documents for this
Thanks,
VenkatThe collation determines the sort rules, so you cannot specify a Collation
and apply different sort rules.
Consider two other important issues:
- a collation applied to a single database involves problems regarding the
collation of the other databases of the same instance (eg. master, msdb, etc).
To resolve this issue is better apply a specific collation to the table
columns (very tedious but...).
the Latin1_general_cs_as sorts upper case and lower case separately but in a
different way among Latin1_General_BIN;I don't remember exactly which one,
but one sorts all the upper cases together separately among the lower case,
the other sorts instead A with a, B with b and so on.
Remeber furthermore tha the new collation does'nt convert the collation of
data already present in your tables.
"Venkat" wrote:
> Hi,
> I want to specify case sensitivity for my database, but at the same time i
> want let customer decide the sort order.
> What i mean is: take the following collation property
> SQL_Latin1_general_cs_as
> in the above property, i want to specify only CS, and let cusotmer decide
> what to (example: what sort order) specify.
> Is it possible? How to do this? I hope this is a very natural requirement,
> but could find help in MS documents for this
> Thanks,
> Venkat
>
>|||Hi,
I would like to understand your statement:
" collation applied to a single database involves problems regarding the
collation of the other databases of the same instance (eg. master, msdb,
etc)."
What is the problem if my database is in diffrent collaiton than the master
database?
I am sure this is possible and there would be no issuees with this.
There might be issues with tempdb, so you can specify collation when you are
creating temp tables.
Can you tell me what is the problems you are expecting if master database
and user database is in diffrent collation?
Other thing you said is: sorting, case sensitivity, accent sensitivity (I
call them as collaiton properties) have to be specified together only?
the reason you said is: all these properties together forms as sort rules?
If so, then when the properties: Latin1, General going to be used and what
purpose they are for? (asume that i have Unicode database)
comments?
Regards,
Venkat
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...
> The collation determines the sort rules, so you cannot specify a Collation
> and apply different sort rules.
> Consider two other important issues:
> - a collation applied to a single database involves problems regarding the
> collation of the other databases of the same instance (eg. master, msdb,
> etc).
> To resolve this issue is better apply a specific collation to the table
> columns (very tedious but...).
> the Latin1_general_cs_as sorts upper case and lower case separately but in
> a
> different way among Latin1_General_BIN;I don't remember exactly which one,
> but one sorts all the upper cases together separately among the lower
> case,
> the other sorts instead A with a, B with b and so on.
> Remeber furthermore tha the new collation does'nt convert the collation
> of
> data already present in your tables.
>
> "Venkat" wrote:
>> Hi,
>> I want to specify case sensitivity for my database, but at the same time
>> i
>> want let customer decide the sort order.
>> What i mean is: take the following collation property
>> SQL_Latin1_general_cs_as
>> in the above property, i want to specify only CS, and let cusotmer decide
>> what to (example: what sort order) specify.
>> Is it possible? How to do this? I hope this is a very natural
>> requirement,
>> but could find help in MS documents for this
>> Thanks,
>> Venkat
>>|||Hi,
i wrote about issues in generic terms: having objects in different
collations COULD be an issue, but not necessarily IS. Surely some (very
little) overhead due to internal conversion is more probable in presence of
more than one collation.
More: the sort order is implicit in the collation you select: BIN (binary)
sort is different among CS_AS or CI_AS or CI_AI etc.
So the Properties Latin1, General are "complementary" with the CS, CI, AS,
AI, KS (etc.) properties: the sort order could be different among each
available combination.
The concept of collation involves not only sort rules but also character set
consideration.
You cannot define o sort order apart from the selected collation.
"Venkat" wrote:
> Hi,
> I would like to understand your statement:
> " collation applied to a single database involves problems regarding the
> collation of the other databases of the same instance (eg. master, msdb,
> etc)."
> What is the problem if my database is in diffrent collaiton than the master
> database?
> I am sure this is possible and there would be no issuees with this.
> There might be issues with tempdb, so you can specify collation when you are
> creating temp tables.
> Can you tell me what is the problems you are expecting if master database
> and user database is in diffrent collation?
> Other thing you said is: sorting, case sensitivity, accent sensitivity (I
> call them as collaiton properties) have to be specified together only?
> the reason you said is: all these properties together forms as sort rules?
> If so, then when the properties: Latin1, General going to be used and what
> purpose they are for? (asume that i have Unicode database)
> comments?
> Regards,
> Venkat
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...
> > The collation determines the sort rules, so you cannot specify a Collation
> > and apply different sort rules.
> > Consider two other important issues:
> > - a collation applied to a single database involves problems regarding the
> > collation of the other databases of the same instance (eg. master, msdb,
> > etc).
> > To resolve this issue is better apply a specific collation to the table
> > columns (very tedious but...).
> >
> > the Latin1_general_cs_as sorts upper case and lower case separately but in
> > a
> > different way among Latin1_General_BIN;I don't remember exactly which one,
> > but one sorts all the upper cases together separately among the lower
> > case,
> > the other sorts instead A with a, B with b and so on.
> >
> > Remeber furthermore tha the new collation does'nt convert the collation
> > of
> > data already present in your tables.
> >
> >
> > "Venkat" wrote:
> >
> >> Hi,
> >> I want to specify case sensitivity for my database, but at the same time
> >> i
> >> want let customer decide the sort order.
> >> What i mean is: take the following collation property
> >> SQL_Latin1_general_cs_as
> >>
> >> in the above property, i want to specify only CS, and let cusotmer decide
> >> what to (example: what sort order) specify.
> >>
> >> Is it possible? How to do this? I hope this is a very natural
> >> requirement,
> >> but could find help in MS documents for this
> >>
> >> Thanks,
> >> Venkat
> >>
> >>
> >>
>
>|||Hi,
I would like to restate what you said about "complimentary" properties like
Latin, General etc.,
As per my understanding these complimentary properties are useful for non
unicode database.
Beucase as per my guess these properties (Latin, General etc.,) specifies
how the data can be stored: in which character set for non unicode database.
Where as these complimnetary properties are of no use (but we still need to
specify) for unicode database.
You have any comments on my understanding?
Regards,
Venkat
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:BF5A2E30-5D28-4129-B025-487DB4F6949D@.microsoft.com...
> Hi,
> i wrote about issues in generic terms: having objects in different
> collations COULD be an issue, but not necessarily IS. Surely some (very
> little) overhead due to internal conversion is more probable in presence
> of
> more than one collation.
> More: the sort order is implicit in the collation you select: BIN (binary)
> sort is different among CS_AS or CI_AS or CI_AI etc.
> So the Properties Latin1, General are "complementary" with the CS, CI, AS,
> AI, KS (etc.) properties: the sort order could be different among each
> available combination.
> The concept of collation involves not only sort rules but also character
> set
> consideration.
> You cannot define o sort order apart from the selected collation.
>
> "Venkat" wrote:
>> Hi,
>> I would like to understand your statement:
>> " collation applied to a single database involves problems regarding the
>> collation of the other databases of the same instance (eg. master, msdb,
>> etc)."
>> What is the problem if my database is in diffrent collaiton than the
>> master
>> database?
>> I am sure this is possible and there would be no issuees with this.
>> There might be issues with tempdb, so you can specify collation when you
>> are
>> creating temp tables.
>> Can you tell me what is the problems you are expecting if master database
>> and user database is in diffrent collation?
>> Other thing you said is: sorting, case sensitivity, accent sensitivity (I
>> call them as collaiton properties) have to be specified together only?
>> the reason you said is: all these properties together forms as sort
>> rules?
>> If so, then when the properties: Latin1, General going to be used and
>> what
>> purpose they are for? (asume that i have Unicode database)
>> comments?
>> Regards,
>> Venkat
>> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
>> message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...
>> > The collation determines the sort rules, so you cannot specify a
>> > Collation
>> > and apply different sort rules.
>> > Consider two other important issues:
>> > - a collation applied to a single database involves problems regarding
>> > the
>> > collation of the other databases of the same instance (eg. master,
>> > msdb,
>> > etc).
>> > To resolve this issue is better apply a specific collation to the table
>> > columns (very tedious but...).
>> >
>> > the Latin1_general_cs_as sorts upper case and lower case separately but
>> > in
>> > a
>> > different way among Latin1_General_BIN;I don't remember exactly which
>> > one,
>> > but one sorts all the upper cases together separately among the lower
>> > case,
>> > the other sorts instead A with a, B with b and so on.
>> >
>> > Remeber furthermore tha the new collation does'nt convert the
>> > collation
>> > of
>> > data already present in your tables.
>> >
>> >
>> > "Venkat" wrote:
>> >
>> >> Hi,
>> >> I want to specify case sensitivity for my database, but at the same
>> >> time
>> >> i
>> >> want let customer decide the sort order.
>> >> What i mean is: take the following collation property
>> >> SQL_Latin1_general_cs_as
>> >>
>> >> in the above property, i want to specify only CS, and let cusotmer
>> >> decide
>> >> what to (example: what sort order) specify.
>> >>
>> >> Is it possible? How to do this? I hope this is a very natural
>> >> requirement,
>> >> but could find help in MS documents for this
>> >>
>> >> Thanks,
>> >> Venkat
>> >>
>> >>
>> >>
>>|||No comments about your understanding.
The question is:
Apart (in unicode evironment) from "localizations" given by the different
available collations (Latin, Japanese, etc), the sort rules are different
between CS, CI, AS, AI,or any combination of them you'll like to select and
the BIN option: anyway, you can make just one choice: so you will provide a
"binary" sort criteria or a case, accent and/or katana sensitivity (or
insensitivity) sorto criteria, depending on the collation you'll set for your
Server, database or column
Regards
Gilberto
"Venkat" wrote:
> Hi,
> I would like to restate what you said about "complimentary" properties like
> Latin, General etc.,
> As per my understanding these complimentary properties are useful for non
> unicode database.
> Beucase as per my guess these properties (Latin, General etc.,) specifies
> how the data can be stored: in which character set for non unicode database.
> Where as these complimnetary properties are of no use (but we still need to
> specify) for unicode database.
> You have any comments on my understanding?
> Regards,
> Venkat
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:BF5A2E30-5D28-4129-B025-487DB4F6949D@.microsoft.com...
> > Hi,
> > i wrote about issues in generic terms: having objects in different
> > collations COULD be an issue, but not necessarily IS. Surely some (very
> > little) overhead due to internal conversion is more probable in presence
> > of
> > more than one collation.
> >
> > More: the sort order is implicit in the collation you select: BIN (binary)
> > sort is different among CS_AS or CI_AS or CI_AI etc.
> > So the Properties Latin1, General are "complementary" with the CS, CI, AS,
> > AI, KS (etc.) properties: the sort order could be different among each
> > available combination.
> > The concept of collation involves not only sort rules but also character
> > set
> > consideration.
> > You cannot define o sort order apart from the selected collation.
> >
> >
> > "Venkat" wrote:
> >
> >> Hi,
> >> I would like to understand your statement:
> >> " collation applied to a single database involves problems regarding the
> >> collation of the other databases of the same instance (eg. master, msdb,
> >> etc)."
> >>
> >> What is the problem if my database is in diffrent collaiton than the
> >> master
> >> database?
> >> I am sure this is possible and there would be no issuees with this.
> >> There might be issues with tempdb, so you can specify collation when you
> >> are
> >> creating temp tables.
> >>
> >> Can you tell me what is the problems you are expecting if master database
> >> and user database is in diffrent collation?
> >>
> >> Other thing you said is: sorting, case sensitivity, accent sensitivity (I
> >> call them as collaiton properties) have to be specified together only?
> >> the reason you said is: all these properties together forms as sort
> >> rules?
> >>
> >> If so, then when the properties: Latin1, General going to be used and
> >> what
> >> purpose they are for? (asume that i have Unicode database)
> >>
> >> comments?
> >>
> >> Regards,
> >> Venkat
> >>
> >> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> >> message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...
> >> > The collation determines the sort rules, so you cannot specify a
> >> > Collation
> >> > and apply different sort rules.
> >> > Consider two other important issues:
> >> > - a collation applied to a single database involves problems regarding
> >> > the
> >> > collation of the other databases of the same instance (eg. master,
> >> > msdb,
> >> > etc).
> >> > To resolve this issue is better apply a specific collation to the table
> >> > columns (very tedious but...).
> >> >
> >> > the Latin1_general_cs_as sorts upper case and lower case separately but
> >> > in
> >> > a
> >> > different way among Latin1_General_BIN;I don't remember exactly which
> >> > one,
> >> > but one sorts all the upper cases together separately among the lower
> >> > case,
> >> > the other sorts instead A with a, B with b and so on.
> >> >
> >> > Remeber furthermore tha the new collation does'nt convert the
> >> > collation
> >> > of
> >> > data already present in your tables.
> >> >
> >> >
> >> > "Venkat" wrote:
> >> >
> >> >> Hi,
> >> >> I want to specify case sensitivity for my database, but at the same
> >> >> time
> >> >> i
> >> >> want let customer decide the sort order.
> >> >> What i mean is: take the following collation property
> >> >> SQL_Latin1_general_cs_as
> >> >>
> >> >> in the above property, i want to specify only CS, and let cusotmer
> >> >> decide
> >> >> what to (example: what sort order) specify.
> >> >>
> >> >> Is it possible? How to do this? I hope this is a very natural
> >> >> requirement,
> >> >> but could find help in MS documents for this
> >> >>
> >> >> Thanks,
> >> >> Venkat
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
I want to specify case sensitivity for my database, but at the same time i
want let customer decide the sort order.
What i mean is: take the following collation property
SQL_Latin1_general_cs_as
in the above property, i want to specify only CS, and let cusotmer decide
what to (example: what sort order) specify.
Is it possible? How to do this? I hope this is a very natural requirement,
but could find help in MS documents for this
Thanks,
VenkatThe collation determines the sort rules, so you cannot specify a Collation
and apply different sort rules.
Consider two other important issues:
- a collation applied to a single database involves problems regarding the
collation of the other databases of the same instance (eg. master, msdb, etc).
To resolve this issue is better apply a specific collation to the table
columns (very tedious but...).
the Latin1_general_cs_as sorts upper case and lower case separately but in a
different way among Latin1_General_BIN;I don't remember exactly which one,
but one sorts all the upper cases together separately among the lower case,
the other sorts instead A with a, B with b and so on.
Remeber furthermore tha the new collation does'nt convert the collation of
data already present in your tables.
"Venkat" wrote:
> Hi,
> I want to specify case sensitivity for my database, but at the same time i
> want let customer decide the sort order.
> What i mean is: take the following collation property
> SQL_Latin1_general_cs_as
> in the above property, i want to specify only CS, and let cusotmer decide
> what to (example: what sort order) specify.
> Is it possible? How to do this? I hope this is a very natural requirement,
> but could find help in MS documents for this
> Thanks,
> Venkat
>
>|||Hi,
I would like to understand your statement:
" collation applied to a single database involves problems regarding the
collation of the other databases of the same instance (eg. master, msdb,
etc)."
What is the problem if my database is in diffrent collaiton than the master
database?
I am sure this is possible and there would be no issuees with this.
There might be issues with tempdb, so you can specify collation when you are
creating temp tables.
Can you tell me what is the problems you are expecting if master database
and user database is in diffrent collation?
Other thing you said is: sorting, case sensitivity, accent sensitivity (I
call them as collaiton properties) have to be specified together only?
the reason you said is: all these properties together forms as sort rules?
If so, then when the properties: Latin1, General going to be used and what
purpose they are for? (asume that i have Unicode database)
comments?
Regards,
Venkat
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...
> The collation determines the sort rules, so you cannot specify a Collation
> and apply different sort rules.
> Consider two other important issues:
> - a collation applied to a single database involves problems regarding the
> collation of the other databases of the same instance (eg. master, msdb,
> etc).
> To resolve this issue is better apply a specific collation to the table
> columns (very tedious but...).
> the Latin1_general_cs_as sorts upper case and lower case separately but in
> a
> different way among Latin1_General_BIN;I don't remember exactly which one,
> but one sorts all the upper cases together separately among the lower
> case,
> the other sorts instead A with a, B with b and so on.
> Remeber furthermore tha the new collation does'nt convert the collation
> of
> data already present in your tables.
>
> "Venkat" wrote:
>> Hi,
>> I want to specify case sensitivity for my database, but at the same time
>> i
>> want let customer decide the sort order.
>> What i mean is: take the following collation property
>> SQL_Latin1_general_cs_as
>> in the above property, i want to specify only CS, and let cusotmer decide
>> what to (example: what sort order) specify.
>> Is it possible? How to do this? I hope this is a very natural
>> requirement,
>> but could find help in MS documents for this
>> Thanks,
>> Venkat
>>|||Hi,
i wrote about issues in generic terms: having objects in different
collations COULD be an issue, but not necessarily IS. Surely some (very
little) overhead due to internal conversion is more probable in presence of
more than one collation.
More: the sort order is implicit in the collation you select: BIN (binary)
sort is different among CS_AS or CI_AS or CI_AI etc.
So the Properties Latin1, General are "complementary" with the CS, CI, AS,
AI, KS (etc.) properties: the sort order could be different among each
available combination.
The concept of collation involves not only sort rules but also character set
consideration.
You cannot define o sort order apart from the selected collation.
"Venkat" wrote:
> Hi,
> I would like to understand your statement:
> " collation applied to a single database involves problems regarding the
> collation of the other databases of the same instance (eg. master, msdb,
> etc)."
> What is the problem if my database is in diffrent collaiton than the master
> database?
> I am sure this is possible and there would be no issuees with this.
> There might be issues with tempdb, so you can specify collation when you are
> creating temp tables.
> Can you tell me what is the problems you are expecting if master database
> and user database is in diffrent collation?
> Other thing you said is: sorting, case sensitivity, accent sensitivity (I
> call them as collaiton properties) have to be specified together only?
> the reason you said is: all these properties together forms as sort rules?
> If so, then when the properties: Latin1, General going to be used and what
> purpose they are for? (asume that i have Unicode database)
> comments?
> Regards,
> Venkat
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...
> > The collation determines the sort rules, so you cannot specify a Collation
> > and apply different sort rules.
> > Consider two other important issues:
> > - a collation applied to a single database involves problems regarding the
> > collation of the other databases of the same instance (eg. master, msdb,
> > etc).
> > To resolve this issue is better apply a specific collation to the table
> > columns (very tedious but...).
> >
> > the Latin1_general_cs_as sorts upper case and lower case separately but in
> > a
> > different way among Latin1_General_BIN;I don't remember exactly which one,
> > but one sorts all the upper cases together separately among the lower
> > case,
> > the other sorts instead A with a, B with b and so on.
> >
> > Remeber furthermore tha the new collation does'nt convert the collation
> > of
> > data already present in your tables.
> >
> >
> > "Venkat" wrote:
> >
> >> Hi,
> >> I want to specify case sensitivity for my database, but at the same time
> >> i
> >> want let customer decide the sort order.
> >> What i mean is: take the following collation property
> >> SQL_Latin1_general_cs_as
> >>
> >> in the above property, i want to specify only CS, and let cusotmer decide
> >> what to (example: what sort order) specify.
> >>
> >> Is it possible? How to do this? I hope this is a very natural
> >> requirement,
> >> but could find help in MS documents for this
> >>
> >> Thanks,
> >> Venkat
> >>
> >>
> >>
>
>|||Hi,
I would like to restate what you said about "complimentary" properties like
Latin, General etc.,
As per my understanding these complimentary properties are useful for non
unicode database.
Beucase as per my guess these properties (Latin, General etc.,) specifies
how the data can be stored: in which character set for non unicode database.
Where as these complimnetary properties are of no use (but we still need to
specify) for unicode database.
You have any comments on my understanding?
Regards,
Venkat
"Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
message news:BF5A2E30-5D28-4129-B025-487DB4F6949D@.microsoft.com...
> Hi,
> i wrote about issues in generic terms: having objects in different
> collations COULD be an issue, but not necessarily IS. Surely some (very
> little) overhead due to internal conversion is more probable in presence
> of
> more than one collation.
> More: the sort order is implicit in the collation you select: BIN (binary)
> sort is different among CS_AS or CI_AS or CI_AI etc.
> So the Properties Latin1, General are "complementary" with the CS, CI, AS,
> AI, KS (etc.) properties: the sort order could be different among each
> available combination.
> The concept of collation involves not only sort rules but also character
> set
> consideration.
> You cannot define o sort order apart from the selected collation.
>
> "Venkat" wrote:
>> Hi,
>> I would like to understand your statement:
>> " collation applied to a single database involves problems regarding the
>> collation of the other databases of the same instance (eg. master, msdb,
>> etc)."
>> What is the problem if my database is in diffrent collaiton than the
>> master
>> database?
>> I am sure this is possible and there would be no issuees with this.
>> There might be issues with tempdb, so you can specify collation when you
>> are
>> creating temp tables.
>> Can you tell me what is the problems you are expecting if master database
>> and user database is in diffrent collation?
>> Other thing you said is: sorting, case sensitivity, accent sensitivity (I
>> call them as collaiton properties) have to be specified together only?
>> the reason you said is: all these properties together forms as sort
>> rules?
>> If so, then when the properties: Latin1, General going to be used and
>> what
>> purpose they are for? (asume that i have Unicode database)
>> comments?
>> Regards,
>> Venkat
>> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
>> message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...
>> > The collation determines the sort rules, so you cannot specify a
>> > Collation
>> > and apply different sort rules.
>> > Consider two other important issues:
>> > - a collation applied to a single database involves problems regarding
>> > the
>> > collation of the other databases of the same instance (eg. master,
>> > msdb,
>> > etc).
>> > To resolve this issue is better apply a specific collation to the table
>> > columns (very tedious but...).
>> >
>> > the Latin1_general_cs_as sorts upper case and lower case separately but
>> > in
>> > a
>> > different way among Latin1_General_BIN;I don't remember exactly which
>> > one,
>> > but one sorts all the upper cases together separately among the lower
>> > case,
>> > the other sorts instead A with a, B with b and so on.
>> >
>> > Remeber furthermore tha the new collation does'nt convert the
>> > collation
>> > of
>> > data already present in your tables.
>> >
>> >
>> > "Venkat" wrote:
>> >
>> >> Hi,
>> >> I want to specify case sensitivity for my database, but at the same
>> >> time
>> >> i
>> >> want let customer decide the sort order.
>> >> What i mean is: take the following collation property
>> >> SQL_Latin1_general_cs_as
>> >>
>> >> in the above property, i want to specify only CS, and let cusotmer
>> >> decide
>> >> what to (example: what sort order) specify.
>> >>
>> >> Is it possible? How to do this? I hope this is a very natural
>> >> requirement,
>> >> but could find help in MS documents for this
>> >>
>> >> Thanks,
>> >> Venkat
>> >>
>> >>
>> >>
>>|||No comments about your understanding.
The question is:
Apart (in unicode evironment) from "localizations" given by the different
available collations (Latin, Japanese, etc), the sort rules are different
between CS, CI, AS, AI,or any combination of them you'll like to select and
the BIN option: anyway, you can make just one choice: so you will provide a
"binary" sort criteria or a case, accent and/or katana sensitivity (or
insensitivity) sorto criteria, depending on the collation you'll set for your
Server, database or column
Regards
Gilberto
"Venkat" wrote:
> Hi,
> I would like to restate what you said about "complimentary" properties like
> Latin, General etc.,
> As per my understanding these complimentary properties are useful for non
> unicode database.
> Beucase as per my guess these properties (Latin, General etc.,) specifies
> how the data can be stored: in which character set for non unicode database.
> Where as these complimnetary properties are of no use (but we still need to
> specify) for unicode database.
> You have any comments on my understanding?
> Regards,
> Venkat
> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> message news:BF5A2E30-5D28-4129-B025-487DB4F6949D@.microsoft.com...
> > Hi,
> > i wrote about issues in generic terms: having objects in different
> > collations COULD be an issue, but not necessarily IS. Surely some (very
> > little) overhead due to internal conversion is more probable in presence
> > of
> > more than one collation.
> >
> > More: the sort order is implicit in the collation you select: BIN (binary)
> > sort is different among CS_AS or CI_AS or CI_AI etc.
> > So the Properties Latin1, General are "complementary" with the CS, CI, AS,
> > AI, KS (etc.) properties: the sort order could be different among each
> > available combination.
> > The concept of collation involves not only sort rules but also character
> > set
> > consideration.
> > You cannot define o sort order apart from the selected collation.
> >
> >
> > "Venkat" wrote:
> >
> >> Hi,
> >> I would like to understand your statement:
> >> " collation applied to a single database involves problems regarding the
> >> collation of the other databases of the same instance (eg. master, msdb,
> >> etc)."
> >>
> >> What is the problem if my database is in diffrent collaiton than the
> >> master
> >> database?
> >> I am sure this is possible and there would be no issuees with this.
> >> There might be issues with tempdb, so you can specify collation when you
> >> are
> >> creating temp tables.
> >>
> >> Can you tell me what is the problems you are expecting if master database
> >> and user database is in diffrent collation?
> >>
> >> Other thing you said is: sorting, case sensitivity, accent sensitivity (I
> >> call them as collaiton properties) have to be specified together only?
> >> the reason you said is: all these properties together forms as sort
> >> rules?
> >>
> >> If so, then when the properties: Latin1, General going to be used and
> >> what
> >> purpose they are for? (asume that i have Unicode database)
> >>
> >> comments?
> >>
> >> Regards,
> >> Venkat
> >>
> >> "Gilberto Zampatti" <GilbertoZampatti@.discussions.microsoft.com> wrote in
> >> message news:7E4D942B-9CEE-46E8-805B-F64233738B04@.microsoft.com...
> >> > The collation determines the sort rules, so you cannot specify a
> >> > Collation
> >> > and apply different sort rules.
> >> > Consider two other important issues:
> >> > - a collation applied to a single database involves problems regarding
> >> > the
> >> > collation of the other databases of the same instance (eg. master,
> >> > msdb,
> >> > etc).
> >> > To resolve this issue is better apply a specific collation to the table
> >> > columns (very tedious but...).
> >> >
> >> > the Latin1_general_cs_as sorts upper case and lower case separately but
> >> > in
> >> > a
> >> > different way among Latin1_General_BIN;I don't remember exactly which
> >> > one,
> >> > but one sorts all the upper cases together separately among the lower
> >> > case,
> >> > the other sorts instead A with a, B with b and so on.
> >> >
> >> > Remeber furthermore tha the new collation does'nt convert the
> >> > collation
> >> > of
> >> > data already present in your tables.
> >> >
> >> >
> >> > "Venkat" wrote:
> >> >
> >> >> Hi,
> >> >> I want to specify case sensitivity for my database, but at the same
> >> >> time
> >> >> i
> >> >> want let customer decide the sort order.
> >> >> What i mean is: take the following collation property
> >> >> SQL_Latin1_general_cs_as
> >> >>
> >> >> in the above property, i want to specify only CS, and let cusotmer
> >> >> decide
> >> >> what to (example: what sort order) specify.
> >> >>
> >> >> Is it possible? How to do this? I hope this is a very natural
> >> >> requirement,
> >> >> but could find help in MS documents for this
> >> >>
> >> >> Thanks,
> >> >> Venkat
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
Subscribe to:
Posts (Atom)