Viewing 6 posts - 1 through 6 (of 6 total)
Here is KB article ( http://support.microsoft.com/kb/977100/ )explaining about the issue we have raised and possible workarounds in case anyone is interested.
January 5, 2010 at 5:39 pm
Update: There is a bug in microsoft sql server's Hash Map join plan when it comes to # based temp tables.
To suppress this error(workaround given by Microsoft team): Include order...
October 28, 2009 at 11:57 am
Update:
We had a live meeting session with microsoft support where they have debugged this behavior. There is no resolution yet, and might be a bug on their side.
August 19, 2009 at 12:14 pm
No, the FK on DocumentChild1 was created at the time of table creation.
Can multiple asynchronous inserts in the Document table can cause this behavior? I mean may be the index...
August 17, 2009 at 5:44 pm
I am wondering do indexes on the table play part in this FK constraint violation error.
I have a unique index on DocumentChild2(Document_GID,Child2_name).
August 17, 2009 at 2:41 pm
My transaction isolation level is READ_COMMITTED and yes, I am using nolocks while reading data from DocumentChild1. But, I have verified that no one is changing(Insert/Update/Delete) data in the DocumentChild1...
August 17, 2009 at 2:11 pm
Viewing 6 posts - 1 through 6 (of 6 total)