Is it possible to get the properties retrievable with T-SQL
SERVERPROPERTY via COM access instead? Do you know some sqlserver COM
object that can provide this kind of information (e.g. LicenseType or
NumLicenses)? Any Ideas?You could use SQL DMO object model. See SQL Server Books Online for more
info. See SQLServer2 object for a start.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Holger" <atlan@.tournedos.de> wrote in message
news:1124040877.686226.191970@.g43g2000cwa.googlegroups.com...
> Is it possible to get the properties retrievable with T-SQL
> SERVERPROPERTY via COM access instead? Do you know some sqlserver COM
> object that can provide this kind of information (e.g. LicenseType or
> NumLicenses)? Any Ideas?
>|||Thank you for your reply but in COM programming it is always good to
read the manual first. The object SQLServer2 does not provide access to
the properties LicenseType or NumLicenses exposed by SERVERPROPERTY.
These properties are of special interest to me. Any further object you
can recommend?|||Another approach is simply the registry to get these values
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\M
icrosoft SQL
Server\80\MSSQLLicenseInfo\MSSQL8.00]
"ConcurrentLimit"=dword:00000006
"Mode"=dword:00000002
Mode = 2 means PerProcessor
Mode != 2 means PerSeat
ConcurrentLimit = Number of Seats OR Processors
Just to complete this topic,
Holger
Showing posts with label properties. Show all posts
Showing posts with label properties. Show all posts
Sunday, March 11, 2012
Saturday, February 25, 2012
Column Properties Window Bug in Management Studio?
This issue deals with where to see the default value for a column in Sql Server 2005 Management Studio.
I have a default value of (1) in a column of type bit:
If you right click on the column in Management Studio object explorer and choose properties, the default value does not appear under "Default Binding" or "Default Schema" in the Column Properties window.
If you select the table and then choose View -> Summary, double click on the Columns folder, then right click -> properties on the column, again the default value does not appear under "Default Binding" or "Default Schema" in the Column Properties window.
If you right click on the table or column and choose "Modify", then select the column, the default value appears in "Default Value or Binding".
If you script the table out (right click -> Script Table as -> Create to), the default value for that column appears in the script.
I'm wondering if this is by design or a bug? Obviously right click-> properties is not a reliable way to view the properties on a column.
Hello Eric,
This issue seems to be a bug in Column Properties page. Could you please report this issue through Connect web site
https://connect.microsoft.com/SQLServer/Feedback
Click on Submit Feedback
Thanks
Sethu Srinivasan
SQL Server Manageability Dev Team
Sunday, February 19, 2012
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)