WARNING. A simple cut and paste of 8 records can distroy a SQL Server table

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: pete (pete_at_madpete.freeserve.co.uk)
Date: 06/18/04


Date: Fri, 18 Jun 2004 11:38:42 +0100

Today I need to copy 8 records in a table. I have to use Access 200 because
of the limitation of Enterprise Manager's inability to cope with field with
more than 900 characters. Selected records, cut, paste. I got an erroor
message about not being able to have a null Key_ID (I copied the reords and
tried to paste the Key_ID as part of the records - normally I hide the
Key_ID).
Now I can't access either the new records or the originals that I was trying
to copy (because, it would seem, they have identical primary keys). I also
cannot export the table via DTS 'unspecified error' and 'integrity
violation'.
Or delete the offending records with a Query Anaylyser delete query.
Basically the entire SQL Server database has been destroyed with a couple of
keystrokes.
Now, I've being developing database applications for over 20years and the
one thing, maybe the only thing I expect from a database server is to
protect the integrity of my data. SQL Server does not, it would seem. These
records aren't just any random unimportant records either. They contain the
'create views' that my entire application require to function and each one
approaches the 8000 record limit and have take years to perfect and just
checking that the table is valid could take me days.



Relevant Pages

  • Re: Data integrity
    ... I do not expect 100% integrity, what I mean by that is "as ... mechanisms in the database and I have to use fingerprints ... SQL server provides guarantee against possible data damage ...
    (microsoft.public.sqlserver.security)
  • WARNING. A simple cut and paste of 8 records can distroy a SQL Server table
    ... Or delete the offending records with a Query Anaylyser delete query. ... I've being developing database applications for over 20years and the ... protect the integrity of my data. ... SQL Server does not, it would seem. ...
    (microsoft.public.sqlserver.server)
  • Re: DB Integrity Check
    ... You still have a database corruption issue that you need to address. ... Microsoft SQL Server MVP ... The Maintanence Plan must put the database ... SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan ...
    (microsoft.public.sqlserver.setup)
  • Re: WARNING. A simple cut and paste of 8 records can distroy a SQL Server table
    ... are you able to drop the constraints on the table, ... > Or delete the offending records with a Query Anaylyser delete query. ... > Basically the entire SQL Server database has been destroyed with a couple ... SQL Server does not, it would seem. ...
    (microsoft.public.sqlserver.server)
  • Re: WARNING. A simple cut and paste of 8 records can distroy a SQL Server table
    ... are you able to drop the constraints on the table, ... > Or delete the offending records with a Query Anaylyser delete query. ... > Basically the entire SQL Server database has been destroyed with a couple ... SQL Server does not, it would seem. ...
    (microsoft.public.sqlserver.programming)