In earlier versions than 2000, you determined whether it is case sensitive at install time. In
SQL2K, you define collation for the system db's at install time. You can specify some other
collation as default for the db when you create the db. And you can divert from db default
collation in CREATE TABLE. Run below to see collation for the columns:
EXEC sp_help tblname
Tibor Karaszi, SQL Server MVP
Archive at: [url]http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver[/url]
"amit" <amit_agarwal20yahoo.co.in> wrote in message
news:083001c347a2$6e08a440$a401280aphx.gbl...> I did the following:
> 1. create table amit (name varchar(10) not null Primary
> 2. insert into amit values ('a')
> 3. select * from amit
> 4. insert into amit values ('A')
> When I fired the insert statement as in 4th step, i
> got 'Violation of primary key constraint.'
> Can anyone tell me is SQL Server Case insensitive.
> If it really is case insensitive then I am sure there must
> be some global option for making it case sensitive.
> Actually I am from Oracle background, and haven't spent
> much time in SQL Server 2000. What I know off is Oracle
> being case sensitive.
> Thanking in advance for help extended.