Thread: Table Error

Hi people
My friend made a .net app for someone and now he is getting this error from 1 table. This error comes when viewed from aspx page and also when he tried to view table records of the database.

Table error: Database ID 8, object ID 402100473, index ID 0. Chain linkage mismatch. (1:482)->next = (1:483), but (1:483)->prev = (1:484).

Any ideas what it relates to?

SQL Server 2000

sounds like a corruption in the database/table. have him run in the database DBCC CheckDB.

Originally Posted by mehere

sounds like a corruption in the database/table. have him run in the database DBCC CheckDB.

DBCC CheckDB....... whats that?

How is it run?

M,

You may need to repair that object. Have a look at this: DBCC CHECKDB (Transact-SQL)

Ya i found that J, thanx

Let me see if he can run that query

So the news came in today is that 1 particular table gets corrupt!!
That table gets entries from many simultaneous users.

So can the table corrupt if 2 records get entered at same time and get same primary key(which is set to auto-increment)??

I've never heard of this happening, M...but maybe one of our database gurus can clarify on that.

Originally Posted by jmurrayhead

I've never heard of this happening, M...but maybe one of our database gurus can clarify on that.

Neither did i heard about it J.

But if this one table is getting corrupt again and again, there must be coding issue, i think.

I thought SQL server was designed to handle that kind of thing, as it locks out simultaneous changes. If your proposed scenario is indeed the case, it could be that you are overcoming the usual protections somehow in code. I've never seen that before... but it may be something like an overridden setting, or a hint option ( for example NOLOCK() )

Originally Posted by Lauramc

I thought SQL server was designed to handle that kind of thing, as it locks out simultaneous changes. If your proposed scenario is indeed the case, it could be that you are overcoming the usual protections somehow in code. I've never seen that before... but it may be something like an overridden setting, or a hint option ( for example NOLOCK() )

Hmm, let my friend change some code and see.

Whats the syntax to lock database when inserting a record??
Its SQL Server 2000.