|
Posted by Roy Harvey on 06/20/07 20:19
I've never seen or heard of a row going missing either, and I spent
plenty of time using 7.0.
Along with what Alex suggested I would suggest doing a complete set of
DBCC integrity checks on the database.
Roy Harvey
Beacon Falls, CT
On Wed, 20 Jun 2007 19:53:32 GMT, "Neil" <nospam@nospam.net> wrote:
>We are running SQL 7 with a front end that links to the tables through ODBC.
>In our main table, the user has no way to delete a record through the
>interface, though it is possible to delete it by opening the ODBC link.
>Users would have no reason to delete a record, but one of our records turned
>up missing.
>
>Now, it's possible that a user may have accidentally deleted the record.
>But, since users don't have any reason to delete records, and since they
>don't access the ODBC links, it seems unlikely (though possible).
>
>I was wondering if anyone had every heard of SQL Server ever "losing" a
>record that had previously been saved. I checked the nightly backup from the
>night after it was added, and the record was there. So either a user deleted
>it, or somehow it got lost in SQL Server. I have no code that deletes
>records in this table in any way, shape or form, so it couldn't have been
>malfunctioning code.
>
>So, while I have a hard time believing that SQL Server would just "lose" a
>record, I also know that anything's possible, so I thought I'd ask if anyone
>had ever heard of such a thing.
>
>Thanks!
>
>Neil
[Back to original message]
|