Showing posts with label entry. Show all posts
Showing posts with label entry. Show all posts

Monday, March 26, 2012

Row will not update or delete using Database Explorer (VWD Express)

Hi

I'm trying to update a database table through Database explorer and occassionally when I try to change an entry it will not update or delete. I therefore have a corrupt record which I can't get rid off and therefore can't use the table. The error report is as follows:

"...A problem occurred attempting to delete row 29

Error Source: Microsoft.VisualStudio.DataTools.

Error Message: The row value(s) updated or deleted either do not make the row unique or they alter multiple rows(2 rows)

Correct the errors and attempt to delete the row again or press ESC to cancel the change(s)..."

All columns allow Nulls and there is no primary key or foreign key relationships with other tables.

Can anyone suggest what I am doing wrong or will I just have to resort to data entry using an ASP.Net control such as Detailsview.

Cheers

Chris


Error Message: The row value(s) updated or deleted either do not make the row unique or they alter multiple rows(2 rows)

In SQL Server, there MUST be a way to uniquely identify a row for a DELETE or UPDATE action. IF the row(s) you are attempting to DELETE are duplicate to other rows, you will not be allowed to delete them.

You options are to create either an IDENTITY field in the table, or a PRIMARY KEY -both of which will uniquely identify the row -allowing deletes to occur.

|||

Arnie

Thank you for your quick response and for your clear explanation as to the problem. I can now delete the rows.

Many thanks

Chris

Friday, March 23, 2012

Row versioning in SQL 2000?

I replicate (transactional replication) my data entry database to a
read-only database. Both are SQL 2000+SP4. The web server reads the
read-only database. At times, there will be lots of changes in the data
entry database, thus lots of replications to the read-only database. I
am concerned that the replication may lock the data in the read-only
database, causing slow response to the web server.

I would like to use row versioning so that the read-only database can
supply old data when the same row is being written by replication. I
read that row versioning is a feature in SQL 2005. Is there any
versioning capability in SQL 2000?

Thanks(betbubble@.gmail.com) writes:

Quote:

Originally Posted by

I replicate (transactional replication) my data entry database to a
read-only database. Both are SQL 2000+SP4. The web server reads the
read-only database. At times, there will be lots of changes in the data
entry database, thus lots of replications to the read-only database. I
am concerned that the replication may lock the data in the read-only
database, causing slow response to the web server.
>
I would like to use row versioning so that the read-only database can
supply old data when the same row is being written by replication. I
read that row versioning is a feature in SQL 2005. Is there any
versioning capability in SQL 2000?


No.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx