Optimistic Concurrnecy Control Error

[sagn]

Hi

This is not so much a programming problem as a data change commitment problem.

I have a table, newly made... no one else has access to it.
No other operations are being performed on this table.

I open it in SQL server 2005. I edit data in the table manually. Some of the rows however give an Optimistic Concurrency Control Error.
I am asked if I want to commit anyway. I hit 'Yes' but the data is not commited and the error message states that the data has been changed since it was last retrieved.

Why is this happening? I really have to edit this data manually as every entry must be eyed and a blanket UPDATE statement is just not feasible.

The table has not keys, indexes, nothing. It is a simple
three column table.

Thanks for any suggestions!

 

[Catadmin]

No triggers?

You haven't been playing the 2k5's DDL triggers, have you, and accidently forgotten to turn them off?

And you're sure no jobs or SSIS packages are accessing that table?



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[mrdenny]

Are you using TEXT or NTEXT data types?

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[sagn]

Nope, Absolutely nothing is accessing this table. I am 100% certain of that. However, the field I want to enter is ntext datatype.

Is that the problem? And if so, why would that be?

Thanks!

 

[sagn]

I made another column of type VARCHAR. I updated that column using UPDATE TABLE
Set VARCHARCol = convert(VARCHAR(500),NTEXTCOL)

Then I tried to manually update the varcharcol. Still no luck! Again there are only certain columns I cannot update in this fashion, ever.

So, Being frustrated I opened the table in SQLServer 2000.
I can now edit the columns and I do not get that error.

Any thoughts?

thanks

 

[SQLSister]

why not add an identity field to the table? That would give it a unique record to base the update on. I never make a table without a unique key in it.

Questions about posting. See faq183-874

 

[mrdenny]

Is this a SQL 2000 server which you are connecting to with the SQL 2005 GUI?

Have you applied SQL 2005 SP1 to the machine with the SQL 2005 GUI on it? SP1 fixes many issues.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com