Re: Foreign key constraints problem in SNC SQL Native client



I think, I would not give clear idea about this issue. let me puting
it in differant way.

This isn't any more clear and isn't any more useful than what you originally
posted. With such information, the best anyone can do is speculate; the
absence of responses indicates that there simply isn't enough useful
information. I seriously doubt that the change from MSS to SNC has anything
to do with this particular problem. My best guess is that you have migrated
to a new DB server (perhaps changing the version used from 2000 to 2005) and
have not used the same installation/configuration values from the original
server/DB. Either that or your referential integrity/schema has changed
somehow.

You need to take the time to figure out the sequence of "commands" sent by
your application to the database and at least understand if this sequence
differs (and how) from that issued by your previous version/configuration.
You can use the Profiler to identify the statements executed by your
application - take these statements and execute them using any other query
tool and see if they produce the error. I'm guessing that they will - if
so, that indicates your client application is not the problem. If your two
versions of the application execute different sets of statements, then the
problem starts with the client application. Either way, you need to do some
basic debugging work.

Based on your original post, I would have expected your previous
configuration to also generate a constraint error since you cannot delete
the parent before deleting the child. The only way this would not have
caused a constraint problem is if you had actively taken measures in the
schema to compensate for this (using an instead-of trigger or defining the
foreign key constraint with the delete / cacasde option). If this was the
situation, then that takes us back to my previous point - your schema
appears to have changed.


.



Relevant Pages

  • Bug in SQL Server 2000 sp3?
    ... Project nvarcharcollate database_default not null constraint ... If i execute the statement ... I get the following error (and no record shown in the result grid) ...
    (microsoft.public.sqlserver.server)
  • Re: How to disable a precedence contstraint
    ... "Allan Mitchell" wrote: ... path by disabling the steps of the path I do not want to execute. ... The last task in both paths have a constraint that points to the ...
    (microsoft.public.sqlserver.dts)
  • Re: Rule disappeared
    ... hidden constraint that I can't find. ... you can execute: ... > EXEC sp_helpconstraint YourTable ...
    (microsoft.public.sqlserver.server)
  • Re: Selectively executing steps disablestep
    ... >I have a package with many steps. ... >Each step's DisableStep property is valued using an INI ... >The idea is if I only want to execute the odd numbered ... Since disabled step does not match an On Completed constraint, ...
    (microsoft.public.sqlserver.dts)