March 24, 2015 at 12:07 am
Good day,
I have the following scenarios:
1. The first table in question have about 66mil records, and is growing with +- 200k per day. On this table we have a Full Text Index created on two of it's fields - and secondary indexes on the other fields. For maintenance reasons (and possible performance reasons) I want to create partitions on this table.
The question is - what happens underneath with the FTS index? Will it be aligned to each partition? Or is it build as "one" index over the entire table?
We're having some delays with the automatic change tracking on records on this table. Every now and again it will fall behind with about 2000 odd records for some time - causing some issues with the application.
The second question then is - will partitioning help in this case? Thus the inserts in my mind so be a bit faster - as the secondary indexes will be aligned indexes..
2. On the second table we have rather large XML columns. These XML columns are indexed. The problem is, is that my table is getting bloated. So I want to partition the table, so that the historical data can reside on different file groups. We don't really use this data that often. But I don't want to move the data to a separate table.
Now same as the first question - how will the XML indexes be treated? Will it aligned with each file group?
We need to do this, in order to make our backups a bit smaller (only backing up relevant file groups), and our index re-indexing a bit faster.
Hope this makes sense
March 29, 2015 at 12:51 pm
Any pointers on this?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply