February 3, 2012 at 1:54 pm
Does having a row_overflow_data in the allocation unit on a partition table not create indexes properly?
February 3, 2012 at 2:02 pm
goodluck (2/3/2012)
Does having a row_overflow_data in the allocation unit on a partition table not create indexes properly?
Not that I'm aware of... why do you ask, what problems are you seeing?
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
February 3, 2012 at 2:10 pm
Because, the partition table is very slow as though no indexes were built on it. When I ran the sys.dm_db_index_physical_stats on the table, I figured there was a ROW_OVERFLOW_DATA entry. I dropped and recreated indexes on that table and I dont see this entry anymore and the table is much faster.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply