Re: Case sensitive TSQL syntax

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Mark Butler (mredhat_nospam_at_yahoo.com)
Date: 04/18/04 

Date: Sun, 18 Apr 2004 10:14:33 -0400

Thanx Uri that did the trick. Changing from
"LATIN1_GENERAL_BIN"
TO
"SQL_LATIN1_GENERAL_CP1_CI_AS"
did the trick. Again Thanx...

"Uri Dimant" <urid@iscar.co.il> wrote in message
news:eIFZ6dUJEHA.3848@TK2MSFTNGP09.phx.gbl...
> Mark
> I am not sure uderstood you.
> Why do you need it?
> You can use ALTER DATABASE ... to change the default COLLATION
> I tried to give you an idea so modify it for your needs.
> CREATE DATABASE TEST
> GO
> ALTER DATABASE TEST COLLATE Latin1_General_BIN
> GO
> CREATE TABLE TEST..TeST (COL INT NOT NULL)
> GO
> INSERT INTO TEST..TeST VALUES (1) ----Works fine
> GO
> INSERT INTO TEST..test VALUES (1) --- Failed
> ---Server: Msg 208, Level 16, State 1, Line 1
> ---Invalid object name 'TEST..test'.
>
> GO
> DROP DATABASE TE
> "Mark Butler" <mredhat_nospam@yahoo.com> wrote in message
> news:OtXWDWUJEHA.3264@tk2msftngp13.phx.gbl...
> > I have a number of stored procedures that are running on my development
> > machine. When I take those same procedure to a clients machine I get
> > syntactical errors. Actually not syntax but my table names are in lower
> > case and I must change them to upper case to work as in the following:
> >
> > SELECT @a_days = mp_bh_due FROM parmtable
> >
> > would need to be changed to:
> >
> > SELECT @a_days = MP_BH_DUE FROM PARMTABLE
> >
> > in order to work. Both servers are SQL 2000 with the same service
packs.
> > There must be a setting I am not aware of which is different between the
> > servers. If at all possible I do not want to change the stored
> procedures.
> >
> > Is there something I can put in the procedures IE set statement, or is
> this
> > easy to change on the sertev/database setup?
> >
> > TIA
> > Mark
> >
> >
>
>

Relevant Pages