Thank you, Cath!

That is correct. The server collations are different:

• Latin1_General_CS_AS (only the correct case works)
• SQL_Latin1_General_CP1_CI_AS (both cases work)

Thanks again for the explanation!

Regards,

slowjoe

Hello Gail,

thanks for your reply.

I am completely aware of that issue. The example I gave is just a simplification of the real problem. I have to work with an application...

I found out, what is the issue.

First, the table has not been created like

CREATE TABLE TABLE1 (COL1 INT);

but like this:

CREATE TABLE user1.TABLE1 (COL1 INT);

This explains, why it has been put...

Now, I dropped the database (including user 'user1').

Then I recreated the database and added a schema named 'user1'.

Thereafter, I recreated user 'user1' and specified in the 'Database User - New'...

I just noticed that the default schema for user 'user1' is 'dbo'. There is a schema 'user1', too. I tried to change the default schema to 'user1', but after I...

Hello,

I would like to do the same.

I have a box that runs SQL Server 2005 SP2 already. Now I would like to place a SQL Server 2000 installation next to...

Finally, I think, that I have misunderstood something.

I could imagine such a behavior for default settings, which are READ COMMITTED and PAGE-LEVEL LOCKING. Then it would make sense to release...

"Serializable" would make it even worse...

Hello,

thanks for your reply.

Well, this is not exactly, what I was talking about.

First, I should have mentioned that I use ROWLOCK.

Second, I don't say that a query maintains the share...