Case

Being new to SQL Server and comming from an Oracle environment...
When I write queries for Oracle, I have to ensure that my queries are
written to be case sensitive. Now when I write those same queries in SQL
(using .Net) it does not appear to be case sensitive. Is this a database
setting or some setting in .Net which is causing case to be ignored?Hi,
You SQL Server collation must be set as CASE INSENSITIVE.. In this case
there is not difference betweeen Upper and
Lower case characters. If your collation is set to Case Sensitive then you
will have the difference between Upper and Lower case.
See the collation of the server using below command:-
select SERVERPROPERTY ( 'collation' )
Thanks
Hari
SQL Server MVP
"Jim Heavey" <JimHeavey@.discussions.microsoft.com> wrote in message
news:D18CBCF9-EA51-4F72-A70D-61C86378C036@.microsoft.com...
> Being new to SQL Server and comming from an Oracle environment...
> When I write queries for Oracle, I have to ensure that my queries are
> written to be case sensitive. Now when I write those same queries in SQL
> (using .Net) it does not appear to be case sensitive. Is this a database
> setting or some setting in .Net which is causing case to be ignored?
>|||Hari Prasad wrote:
[vbcol=seagreen]
> Hi,
> You SQL Server collation must be set as CASE INSENSITIVE.. In this case
> there is not difference betweeen Upper and
> Lower case characters. If your collation is set to Case Sensitive then you
> will have the difference between Upper and Lower case.
> See the collation of the server using below command:-
> select SERVERPROPERTY ( 'collation' )
> Thanks
> Hari
> SQL Server MVP
>
> "Jim Heavey" <JimHeavey@.discussions.microsoft.com> wrote in message
> news:D18CBCF9-EA51-4F72-A70D-61C86378C036@.microsoft.com...
It depends on collation of your SQL Server.
In your collation if you found CI then that collation is
case-insensitive and if it is CS then it is case-sensitive.
Try this
select * from ::fn_helpcollations()
where name = serverproperty('collation')
Regards
Amish Shah

Case

Being new to SQL Server and comming from an Oracle environment...
When I write queries for Oracle, I have to ensure that my queries are
written to be case sensitive. Now when I write those same queries in SQL
(using .Net) it does not appear to be case sensitive. Is this a database
setting or some setting in .Net which is causing case to be ignored?Hi,
You SQL Server collation must be set as CASE INSENSITIVE.. In this case
there is not difference betweeen Upper and
Lower case characters. If your collation is set to Case Sensitive then you
will have the difference between Upper and Lower case.
See the collation of the server using below command:-
select SERVERPROPERTY ( 'collation' )
Thanks
Hari
SQL Server MVP
"Jim Heavey" <JimHeavey@.discussions.microsoft.com> wrote in message
news:D18CBCF9-EA51-4F72-A70D-61C86378C036@.microsoft.com...
> Being new to SQL Server and comming from an Oracle environment...
> When I write queries for Oracle, I have to ensure that my queries are
> written to be case sensitive. Now when I write those same queries in SQL
> (using .Net) it does not appear to be case sensitive. Is this a database
> setting or some setting in .Net which is causing case to be ignored?
>|||Hari Prasad wrote:
> Hi,
> You SQL Server collation must be set as CASE INSENSITIVE.. In this case
> there is not difference betweeen Upper and
> Lower case characters. If your collation is set to Case Sensitive then you
> will have the difference between Upper and Lower case.
> See the collation of the server using below command:-
> select SERVERPROPERTY ( 'collation' )
> Thanks
> Hari
> SQL Server MVP
>
> "Jim Heavey" <JimHeavey@.discussions.microsoft.com> wrote in message
> news:D18CBCF9-EA51-4F72-A70D-61C86378C036@.microsoft.com...
> > Being new to SQL Server and comming from an Oracle environment...
> > When I write queries for Oracle, I have to ensure that my queries are
> > written to be case sensitive. Now when I write those same queries in SQL
> > (using .Net) it does not appear to be case sensitive. Is this a database
> > setting or some setting in .Net which is causing case to be ignored?
> >
It depends on collation of your SQL Server.
In your collation if you found CI then that collation is
case-insensitive and if it is CS then it is case-sensitive.
Try this
select * from ::fn_helpcollations()
where name = serverproperty('collation')
Regards
Amish Shah

Cascading Parameters in Dev environment Convulsing

I'm usring RS SP2 and have a cascading parameter. Both parameters are drop
down list. When you change the first drop down, the dev environment goes
into convulsions and starts flashing. I've done some research and found this
issue in a few places on the net but have not found a solution. All
indications ar ethat it will work fine once deployed. Anyone know of the
solution to this issue or a work around?I don't have this happen with all cascading parameter reports, just some of
them. I don't have a pattern for when it happens and when it doesn't. For
those reports where this happens I test by deploying to a test server rather
than testing from the dev environment. As you say, they work when deployed.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stephen Farmer" <Stephen.Farmer@.LucrumInc.Com> wrote in message
news:eADozujWFHA.2448@.TK2MSFTNGP12.phx.gbl...
> I'm usring RS SP2 and have a cascading parameter. Both parameters are drop
> down list. When you change the first drop down, the dev environment goes
> into convulsions and starts flashing. I've done some research and found
> this issue in a few places on the net but have not found a solution. All
> indications ar ethat it will work fine once deployed. Anyone know of the
> solution to this issue or a work around?
>
>