SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


No catalog entry found for partition ID....


No catalog entry found for partition ID....

Author
Message
alex-746374
alex-746374
Valued Member
Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)

Group: General Forum Members
Points: 70 Visits: 102

Suggestion:

Change the proc so that the indexes are created after the insert is done. That way the reindex won't be needed and you might get around this problem.


Gail, thanks for your help here too - it's appreciated.

I was wrong. The indexes are added before the temp table is populated. Here's how it goes:

The temp table is created, and indexes added. There's a while loop. Stuff is added into the offending temp table. Then the temp table is reindexed (if you want the SP to fail, that is!), then the temp table is joined on as part of the update of another table. The temp table is truncated at the end of (but still inside) the loop.

So it's possible that the repeated reindexing and truncating is part of the problem. I'll try and have a play with this later.
Paul Randal
Paul Randal
Hall of Fame
Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)

Group: General Forum Members
Points: 3769 Visits: 1717
How many entries are added to the temp table before the index rebuild? Are they added in index key order? Is there a noticeable difference in perf if the index rebuild is removed?

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
GilaMonster
GilaMonster
SSC Guru
SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)SSC Guru (90K reputation)

Group: General Forum Members
Points: 90731 Visits: 45284
and, if you move the creation of the indexes to after the population, do you still get this error? If not, that's possibly a good workaround. It also means you're not getting the overhead of updating indexes while the table's been populated.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Paul Randal
Paul Randal
Hall of Fame
Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)

Group: General Forum Members
Points: 3769 Visits: 1717
Consensus (without proving it yet) is that this looks like a bug. Do you want to push for a hotfix if that turns out to be the case? If so you'll need to call in to Product Support and they'll pick it up. if not, they'll at least investigate and confirm, and then get it into the next release.

Thanks

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Paul Randal
Paul Randal
Hall of Fame
Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)

Group: General Forum Members
Points: 3769 Visits: 1717
Ok - this has now been proven to be a bug inside MS, with a simple repro. Alex - let me know if you want to push for a hotfix for this and I'll give you the internal bug number that's been opened that you can use when you call PSS (and some high-level names to add to make sure you get the correct response).

Thanks for posting about this (and Gail, thanks for pulling me in).

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
alex-746374
alex-746374
Valued Member
Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)

Group: General Forum Members
Points: 70 Visits: 102
Paul Randal (8/14/2009)
Ok - this has now been proven to be a bug inside MS, with a simple repro. Alex - let me know if you want to push for a hotfix for this and I'll give you the internal bug number that's been opened that you can use when you call PSS (and some high-level names to add to make sure you get the correct response).


Thanks for your help. I'm away now for a few weeks. I've left all the details (including your message above) with my colleagues, and they may take you up on this offer. Failing that, I'll get onto it upon my return.

Thanks for your help here, it's been great!

Cheers,
Alex.
alex-746374
alex-746374
Valued Member
Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)

Group: General Forum Members
Points: 70 Visits: 102
Paul Randal (8/14/2009)
Ok - this has now been proven to be a bug inside MS, with a simple repro. Alex - let me know if you want to push for a hotfix for this and I'll give you the internal bug number that's been opened that you can use when you call PSS (and some high-level names to add to make sure you get the correct response).

Thanks for posting about this (and Gail, thanks for pulling me in).


Paul,

That internal bug number would be handy - we're going to go for a hotfix. I've sent you an email - you could reply to that or post the number here, whatever is more convenient for you.

Thanks for your help here,
Alex.
Paul Randal
Paul Randal
Hall of Fame
Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)

Group: General Forum Members
Points: 3769 Visits: 1717
Hi Alex - one of the Principal Escalation Engineers will be contacting you directly. Thanks

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
henrik.litsne
henrik.litsne
Grasshopper
Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)

Group: General Forum Members
Points: 11 Visits: 59
So... What happened with this bug? Has it been fixed? I get the same problem when rebuilding a temp table in a SP.
alex-746374
alex-746374
Valued Member
Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)

Group: General Forum Members
Points: 70 Visits: 102
henrik.litsne (5/23/2010)
So... What happened with this bug? Has it been fixed? I get the same problem when rebuilding a temp table in a SP.


Microsoft can't be bothered to fix it in 2005 because it's too close to end of life or not important enough or something, but have said that it'll go out in a future sp for 2008 (and presumably 2010 but they didn't mention that).
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search