Friday, March 9, 2012

Query optimisor out of stack space

Hi,

I have recently upgraded to SQL Server 2005 (SP1) Developer Edition from SQL Server 2000 (SP4). Since doing so, i have been unable to delete any records from a specific table.

I have found this is due to having approximately 340 foreign key constraints referencing the UserID column of the table.

This functionality worked in SQL Server 2000. Do Microsoft plan to release any fixes for this issue?

Kind Regards,
Martyn...

Wow, 340 FKs?!

I don't think there is going to be a fix for this. The cost for maintaining this constraint is quite large. You should consider simplifying the schema.

http://msdn2.microsoft.com/en-us/library/aa337357.aspx|||

Hello,

are you the Martyn Lawson from Taunus-Sparkasse?

Gru?

moh

|||

Hi,

Just to update you all with this issue. I have raised a formal support call with Microsoft who are currently investigating the issue. They recommend a maximum of 253 FK's on a single table but the absolute maximum is 2966.

The support engineer assigned to my case has told me that although i have exceeded the recommended maximum it should not cause an error and this is indeed a bug.

I am still waiting to here the outcome, but will update this thread as soon as i know anything.

Cheers,

Martyn...

|||No. I am not.

No comments:

Post a Comment