Cannot update record

Question

Cannot update record

Phunhog

SSCommitted

Points: 1562
More actions
March 26, 2009 at 9:14 am

#198591

I have a SQL Server 2000 db and have been trying to update a record in a table. I get error 2147217865, Invalid object named UPDATE. I get the error with an update query as well as trying to enter the data directly to the table.
This normalized relational db has been working perfectly for 5+ years. Any help you may proved will be greatly appreciated
jhh

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

Carolyn Richardson SSCrazy Eights Points: 8357 More actions · Answer 1

I've never seen this error before but a quick search in Google showed users getting this error when not using the correct schema in referring to the table. Could this be your problem?

Facts are stubborn things, but statistics are more pliable - Mark Twain
Carolyn
SQLServerSpecialists[/url]

Phunhog SSCommitted Points: 1562 More actions · Answer 2

Thanks Carolyn, I appreciate the reply.

I've never seen the error either. My google searches turn up the same, and right now the entire table appears to be corrupted.

I'm in damage control mode at the moment going through the restore process.

argh

jhh

steveb. SSC-Forever Points: 46733 More actions · Answer 3

Have you run DBCC CHECKDB to check for corruption in the database.?

Phunhog SSCommitted Points: 1562 More actions · Answer 4

Yes

And I've done a restore. All is well thanks.

jhh

maechismo_8514 SSCoach Points: 17510 More actions · Answer 5

John H. Higgins (3/26/2009)
Yes
And I've done a restore. All is well thanks.
jhh

Are you not doing any root cause analysis and find out where the problem could be? mostly due to hardware resources. Identify the issue or it might spread to the rest of your databases.

steveb. SSC-Forever Points: 46733 More actions · Answer 6

Krishna (3/26/2009)
John H. Higgins (3/26/2009)
Yes
And I've done a restore. All is well thanks.
jhh
Are you not doing any root cause analysis and find out where the problem could be? mostly due to hardware resources. Identify the issue or it might spread to the rest of your databases.

Agreed, this issue may come back and bite you in the future unless you work out the root-cause

Phunhog SSCommitted Points: 1562 More actions · Answer 7

I'm pretty sure the root cause is allowing one of my users to do some editing in the back end

I'm going to let it go at that.

jhh

tosscrosby SSCoach Points: 18045 More actions · Answer 8

Still, a cursory look of the event logs on the server or maybe some disk checks could be well worth the time spent - IMO. I've never seen an application corrupt a table. Maybe screw up data integrity but not corrupt the table. Just my 2 cents....

-- You can't be late until you show up.

maechismo_8514 SSCoach Points: 17510 More actions · Answer 9

John H. Higgins (3/26/2009)
I'm pretty sure the root cause is allowing one of my users to do some editing in the back end
I'm going to let it go at that.
jhh

Application- it;s very unlikely that it will corrupt data. Most of the errors are due to hardware resources and most of them are I/O. It's worth time spending on it, I would say before doing the restore I would have taken a snapshot of it and further investigate into it.