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

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: SWu (sw_at_rgrzz.com.au)
Date: 06/18/04 

Date: Fri, 18 Jun 2004 21:05:06 +1000

sorry if this sounds like a couple of dumb, obvious questions:
- do you have backups of this important code?
- are you able to drop the constraints on the table, remove the offending
records and reapply the constraints?

regards,
stephen
"pete" <pete@madpete.freeserve.co.uk> wrote in message
news:40d2c64e$0$4584$db0fefd9@news.zen.co.uk...
> 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: 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)
  • 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)
  • 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.programming)
  • Re: SQL Server error when attempting to delete a record
    ... What version of SQL Server have you got? ... recordto be affected and execute this command based on the Primary Key ... Script the table's definition to a file (including constraints, indices, ... of the database, factors like that. ...
    (microsoft.public.sqlserver.server)
  • Re: Why must I pass the current date in LINQ when I have a default constraint in my database?
    ... Wow, that's really a kluge work-around, no? ... So does this mean that I have to consider all default constraints in my database worthless and re-create the intended effect on my class in LINQ? ... Of course, it also means you have to override the methods which perform the translation between the Expression and the SQL that is sent to SQL Server, which is probably going to entail a good deal of work. ...
    (microsoft.public.dotnet.languages.csharp)