Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
Wang
Starting Member
48 Posts |
Posted - 2009-02-05 : 11:10:34
|
HiWe have an odd problem with a largish partition table (maybe 5bn rows). It seems to have started quite suddenly - ie it used to work fine!The issue is that now when we insert into it from another partition table it throws an Duplicate Key ignored warning and inserts 0 records. (The PK is defined with ignore_dup_key on).However if we select the same 64 source rows into a temp table and then in from there its fine.If we insert select top 100000 then its fine as well.If we just select the data we can see that it has 64 rows and they are unique as far as the key is concerned.Additionally if I try to generate the query plan I get the following message:An error occurred while executing batch. Error message is: Error processing execution plan results. The error message is:The type initializer for 'Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanNodeBuilder' threw an exception.Exception of type 'System.OutOfMemoryException' was thrown.Any ideas on what is going on here would be appreciated. I am posting in corruption as it strikes me as corruption oriented...CheersRich |
|
Wang
Starting Member
48 Posts |
Posted - 2009-02-06 : 13:01:43
|
Further info.2005 Enterprise. Sp2.I seem to have missed the fact that if we select from the destination table based on the first part of the pk (the part we are inserting has the same restriction clause) there are no results.A reboot has cured the execution plan problem, but not the insert.I tried creating a new table with pk ignore_dup_key on and inserting the offending data into that, and it worked fine, but still not into the partition table. |
|
|
|
|
|