Board index MS SQL Server

data case-insensitive but storedprocedure identifier case-sensitive?

data case-insensitive but storedprocedure identifier case-sensitive?

Post by Sidney Zhan » Fri, 14 Jan 2000 04:00:00



Hi, somebody help me.
I use SQL Server 6.5, originally installed as codepage Chinese 936, and case
insensitive. Everything is OK before
last week, I found that my SQL server is now data case-insensitive and
storedprocedure identifier case-sensitive.

INSERT TMP
('COLUMN1')VALUES('A')
SELECT * FROM tmp WHERE column1 = 'a'    -- can be selected and data
case-insensitive

but




identifier case sensitive

Does anyone encounted this before? Is this a bug or I just SET some hidden
system var , which I don't know.
Before this problem occur, I have installed SQL Server7.0 on the same
machine and test data import and export.
Then switch back to SQL Server 6.5. Is this the reason?
BTW: another SQL Server in same room, encounted the same problem yesterday.
but That machine is pure 6.5, never installed 7.0
I've searched in the SQL documents, but find no answer.
Anyone can help me.
Thanks a lot
Sidney Zhang

 
 
 
Top

data case-insensitive but storedprocedure identifier case-sensitive?

Post by Neil Pik » Fri, 14 Jan 2000 04:00:00


Sidney - definitely sounds like a bug.  You'd have to call MS PSS methinks.

Q.  Who are Microsoft Product Support Services and how do I contact them?
(v1.2  1999.12.16)

A.  These are people who support all MS's products, write fixes, take the
calls, sort out workarounds etc.  They work 24x7x365.  You can call them by
phone (U.S. is 1-800-936-3500)

For details of your nearest PSS support centre and other info try :-

       http://support.microsoft.com/support/supportnet/default.asp
   http://www.microsoft.com/support/customer/itpro.htm

To report on the Web :-

   http://www.microsoft.com/technet/support/incident.htm
   http://support.microsoft.com/support/webresponse.asp

All incidents are chargeable either to your credit card or an existing account.
 The charge WILL be re-imbursed if the problem turns out to be an MS bug, or a
feature that hasn't been publicly documented.  The person answering the phone
cannot know it's a bug, so they have to take details of your credit card before
passing you on to a technician.  When the call is closed the technician decides
whether to mark the call as "free" in which case you get a refund
automatically.  (Same for Web incidents)

 Neil Pike MVP/MCSE.  Protech Computing Ltd
 (Please reply only to newsgroups)
 SQL FAQ (406 entries) see

http://forumsb.compuserve.com/vlforums/UK/default.asp?SRV=MSDevApps
 or www.ntfaq.com/sql.html (+ ntfaq download)
 or http://www.sql-server.co.uk

 
 
 
Top

data case-insensitive but storedprocedure identifier case-sensitive?

Post by Tibor Karasz » Fri, 14 Jan 2000 04:00:00


Sidney,

This is strange indeed. It shouldn't behave this way. There's no SET
parameter or similar to control this. Only way I can think of if is someone
hacked you installation (hacked sysconfigures and managed to get the server
started).

--
Tibor Karaszi
MCDBA, MCSE, MCSD, MCT, SQL Server MVP
Cornerstone Sweden AB
Please reply to the newsgroup only, not by email.


> Hi, somebody help me.
> I use SQL Server 6.5, originally installed as codepage Chinese 936, and
case
> insensitive. Everything is OK before
> last week, I found that my SQL server is now data case-insensitive and
> storedprocedure identifier case-sensitive.

> INSERT TMP
> ('COLUMN1')VALUES('A')
> SELECT * FROM tmp WHERE column1 = 'a'    -- can be selected and data
> case-insensitive

> but




> identifier case sensitive

> Does anyone encounted this before? Is this a bug or I just SET some hidden
> system var , which I don't know.
> Before this problem occur, I have installed SQL Server7.0 on the same
> machine and test data import and export.
> Then switch back to SQL Server 6.5. Is this the reason?
> BTW: another SQL Server in same room, encounted the same problem
yesterday.
> but That machine is pure 6.5, never installed 7.0
> I've searched in the SQL documents, but find no answer.
> Anyone can help me.
> Thanks a lot
> Sidney Zhang


 
 
 
Top

data case-insensitive but storedprocedure identifier case-sensitive?

Post by Sidney Zhan » Sat, 15 Jan 2000 04:00:00


Hacked! Tibor, you fritended me. If there exist a way to make a SQL Server
behave like this, most of our projects are in dangerous. Because, our
project have lots of storedprocedures and all of them are case-insensitive.
Now I don't know which one will refuse to work at someday.
What suggestion do you have?
Thanks
Sidney


> Sidney,

> This is strange indeed. It shouldn't behave this way. There's no SET
> parameter or similar to control this. Only way I can think of if is
someone
> hacked you installation (hacked sysconfigures and managed to get the
server
> started).

> --
> Tibor Karaszi
> MCDBA, MCSE, MCSD, MCT, SQL Server MVP
> Cornerstone Sweden AB
> Please reply to the newsgroup only, not by email.



> > Hi, somebody help me.
> > I use SQL Server 6.5, originally installed as codepage Chinese 936, and
> case
> > insensitive. Everything is OK before
> > last week, I found that my SQL server is now data case-insensitive and
> > storedprocedure identifier case-sensitive.

> > INSERT TMP
> > ('COLUMN1')VALUES('A')
> > SELECT * FROM tmp WHERE column1 = 'a'    -- can be selected and data
> > case-insensitive

> > but




> > identifier case sensitive

> > Does anyone encounted this before? Is this a bug or I just SET some
hidden
> > system var , which I don't know.
> > Before this problem occur, I have installed SQL Server7.0 on the same
> > machine and test data import and export.
> > Then switch back to SQL Server 6.5. Is this the reason?
> > BTW: another SQL Server in same room, encounted the same problem
> yesterday.
> > but That machine is pure 6.5, never installed 7.0
> > I've searched in the SQL documents, but find no answer.
> > Anyone can help me.
> > Thanks a lot
> > Sidney Zhang


 
 
 
Top

data case-insensitive but storedprocedure identifier case-sensitive?

Post by Tibor Karasz » Sat, 15 Jan 2000 04:00:00


That was not my intention. I didn't mean "hacked" as in "hacker-attack". I
meant it as in "some dba, with proper permissions, performed an unsupported
and stupid operation".
If you have control of security, and know who have sa permissions, you can
disregard my guess. (I doubt that my speculation would work that way
anyhow...).

But basically, SQL Server should _not_ behave like you describe...
--
Tibor Karaszi
MCDBA, MCSE, MCSD, MCT, SQL Server MVP
Cornerstone Sweden AB
Please reply to the newsgroup only, not by email.


> Hacked! Tibor, you fritended me. If there exist a way to make a SQL Server
> behave like this, most of our projects are in dangerous. Because, our
> project have lots of storedprocedures and all of them are
case-insensitive.
> Now I don't know which one will refuse to work at someday.
> What suggestion do you have?
> Thanks
> Sidney



> > Sidney,

> > This is strange indeed. It shouldn't behave this way. There's no SET
> > parameter or similar to control this. Only way I can think of if is
> someone
> > hacked you installation (hacked sysconfigures and managed to get the
> server
> > started).

> > --
> > Tibor Karaszi
> > MCDBA, MCSE, MCSD, MCT, SQL Server MVP
> > Cornerstone Sweden AB
> > Please reply to the newsgroup only, not by email.



> > > Hi, somebody help me.
> > > I use SQL Server 6.5, originally installed as codepage Chinese 936,
and
> > case
> > > insensitive. Everything is OK before
> > > last week, I found that my SQL server is now data case-insensitive and
> > > storedprocedure identifier case-sensitive.

> > > INSERT TMP
> > > ('COLUMN1')VALUES('A')
> > > SELECT * FROM tmp WHERE column1 = 'a'    -- can be selected and data
> > > case-insensitive

> > > but




storedprocedure
> > > identifier case sensitive

> > > Does anyone encounted this before? Is this a bug or I just SET some
> hidden
> > > system var , which I don't know.
> > > Before this problem occur, I have installed SQL Server7.0 on the same
> > > machine and test data import and export.
> > > Then switch back to SQL Server 6.5. Is this the reason?
> > > BTW: another SQL Server in same room, encounted the same problem
> > yesterday.
> > > but That machine is pure 6.5, never installed 7.0
> > > I've searched in the SQL documents, but find no answer.
> > > Anyone can help me.
> > > Thanks a lot
> > > Sidney Zhang


 
 
 
Top

data case-insensitive but storedprocedure identifier case-sensitive?

Post by Sidney Zhan » Sat, 15 Jan 2000 04:00:00


I know, but It did.
Thanks again
Sidney


> That was not my intention. I didn't mean "hacked" as in "hacker-attack". I
> meant it as in "some dba, with proper permissions, performed an
unsupported
> and stupid operation".
> If you have control of security, and know who have sa permissions, you can
> disregard my guess. (I doubt that my speculation would work that way
> anyhow...).

> But basically, SQL Server should _not_ behave like you describe...
> --
> Tibor Karaszi
> MCDBA, MCSE, MCSD, MCT, SQL Server MVP
> Cornerstone Sweden AB
> Please reply to the newsgroup only, not by email.



> > Hacked! Tibor, you fritended me. If there exist a way to make a SQL
Server
> > behave like this, most of our projects are in dangerous. Because, our
> > project have lots of storedprocedures and all of them are
> case-insensitive.
> > Now I don't know which one will refuse to work at someday.
> > What suggestion do you have?
> > Thanks
> > Sidney



> > > Sidney,

> > > This is strange indeed. It shouldn't behave this way. There's no SET
> > > parameter or similar to control this. Only way I can think of if is
> > someone
> > > hacked you installation (hacked sysconfigures and managed to get the
> > server
> > > started).

> > > --
> > > Tibor Karaszi
> > > MCDBA, MCSE, MCSD, MCT, SQL Server MVP
> > > Cornerstone Sweden AB
> > > Please reply to the newsgroup only, not by email.



> > > > Hi, somebody help me.
> > > > I use SQL Server 6.5, originally installed as codepage Chinese 936,
> and
> > > case
> > > > insensitive. Everything is OK before
> > > > last week, I found that my SQL server is now data case-insensitive
and
> > > > storedprocedure identifier case-sensitive.

> > > > INSERT TMP
> > > > ('COLUMN1')VALUES('A')
> > > > SELECT * FROM tmp WHERE column1 = 'a'    -- can be selected and data
> > > > case-insensitive

> > > > but




> storedprocedure
> > > > identifier case sensitive

> > > > Does anyone encounted this before? Is this a bug or I just SET some
> > hidden
> > > > system var , which I don't know.
> > > > Before this problem occur, I have installed SQL Server7.0 on the
same
> > > > machine and test data import and export.
> > > > Then switch back to SQL Server 6.5. Is this the reason?
> > > > BTW: another SQL Server in same room, encounted the same problem
> > > yesterday.
> > > > but That machine is pure 6.5, never installed 7.0
> > > > I've searched in the SQL documents, but find no answer.
> > > > Anyone can help me.
> > > > Thanks a lot
> > > > Sidney Zhang


 
 
 
Top

data case-insensitive but storedprocedure identifier case-sensitive?

Post by BPMargoli » Sat, 15 Jan 2000 04:00:00


Sidney,

Run sp_helpsort to confirm that your server is still using the sort order
that you believe it is.


> I know, but It did.
> Thanks again
> Sidney



> > That was not my intention. I didn't mean "hacked" as in "hacker-attack".
I
> > meant it as in "some dba, with proper permissions, performed an
> unsupported
> > and stupid operation".
> > If you have control of security, and know who have sa permissions, you
can
> > disregard my guess. (I doubt that my speculation would work that way
> > anyhow...).

> > But basically, SQL Server should _not_ behave like you describe...
> > --
> > Tibor Karaszi
> > MCDBA, MCSE, MCSD, MCT, SQL Server MVP
> > Cornerstone Sweden AB
> > Please reply to the newsgroup only, not by email.



> > > Hacked! Tibor, you fritended me. If there exist a way to make a SQL
> Server
> > > behave like this, most of our projects are in dangerous. Because, our
> > > project have lots of storedprocedures and all of them are
> > case-insensitive.
> > > Now I don't know which one will refuse to work at someday.
> > > What suggestion do you have?
> > > Thanks
> > > Sidney



> > > > Sidney,

> > > > This is strange indeed. It shouldn't behave this way. There's no SET
> > > > parameter or similar to control this. Only way I can think of if is
> > > someone
> > > > hacked you installation (hacked sysconfigures and managed to get the
> > > server
> > > > started).

> > > > --
> > > > Tibor Karaszi
> > > > MCDBA, MCSE, MCSD, MCT, SQL Server MVP
> > > > Cornerstone Sweden AB
> > > > Please reply to the newsgroup only, not by email.



> > > > > Hi, somebody help me.
> > > > > I use SQL Server 6.5, originally installed as codepage Chinese
936,
> > and
> > > > case
> > > > > insensitive. Everything is OK before
> > > > > last week, I found that my SQL server is now data case-insensitive
> and
> > > > > storedprocedure identifier case-sensitive.

> > > > > INSERT TMP
> > > > > ('COLUMN1')VALUES('A')
> > > > > SELECT * FROM tmp WHERE column1 = 'a'    -- can be selected and
data
> > > > > case-insensitive

> > > > > but




> > storedprocedure
> > > > > identifier case sensitive

> > > > > Does anyone encounted this before? Is this a bug or I just SET
some
> > > hidden
> > > > > system var , which I don't know.
> > > > > Before this problem occur, I have installed SQL Server7.0 on the
> same
> > > > > machine and test data import and export.
> > > > > Then switch back to SQL Server 6.5. Is this the reason?
> > > > > BTW: another SQL Server in same room, encounted the same problem
> > > > yesterday.
> > > > > but That machine is pure 6.5, never installed 7.0
> > > > > I've searched in the SQL documents, but find no answer.
> > > > > Anyone can help me.
> > > > > Thanks a lot
> > > > > Sidney Zhang


 
 
 
Top

data case-insensitive but storedprocedure identifier case-sensitive?

Post by Sidney Zhan » Tue, 18 Jan 2000 04:00:00


Any one who interested in this problem,  and want to see it yourself, email

and I'll tell you where my server is, the login and password. I think , the
problem server could be kept until Wensday 19th Jan. 2000. After then, all
the server will be reinstalled.
Sidney  Zhang


> Hi, somebody help me.
> I use SQL Server 6.5, originally installed as codepage Chinese 936, and
case
> insensitive. Everything is OK before
> last week, I found that my SQL server is now data case-insensitive and
> storedprocedure identifier case-sensitive.

> INSERT TMP
> ('COLUMN1')VALUES('A')
> SELECT * FROM tmp WHERE column1 = 'a'    -- can be selected and data
> case-insensitive

> but




> identifier case sensitive

> Does anyone encounted this before? Is this a bug or I just SET some hidden
> system var , which I don't know.
> Before this problem occur, I have installed SQL Server7.0 on the same
> machine and test data import and export.
> Then switch back to SQL Server 6.5. Is this the reason?
> BTW: another SQL Server in same room, encounted the same problem
yesterday.
> but That machine is pure 6.5, never installed 7.0
> I've searched in the SQL documents, but find no answer.
> Anyone can help me.
> Thanks a lot
> Sidney Zhang


 
 
 
Top

1. case sensitive/ case insensitive -- ?

we are converting applications from Sybase to ss2k. Our applications
were developed with case sensitive settings.

The default setting for ss2k is case insensitive.  

What is the advantage of taking the default install, and using case
insensitive collations?

Are there performance advantages?

What about for connecting with other servers?

What are other installations doing?

Thanks.

Linda

2. Using 'use' dynamically

3. Case sensitive on Case Insensitive DB

4. MDAC 2.5 and MDAC 2.6

5. v6.5 case sensitive to case insensitive ?

6. Changing sort orders in SQL 7.0

7. Case sensitive restored into a Case insensitive DB

8. Database to Run Clarify Call Management Software

9. case-sensitive or case-insensitive: which is better in SQL 7

10. collation problem -- switch from case insensitive to case sensitive

11. How to use both case sensitive and case insensitive search

12. Case-sensitive to Case-insensitive

13. SQL Server case sensitive or case insensitive.


All times are UTC
Board index