May 23, 2013 at 4:29 pm
I have a table with 5 million rows and I want to see if i could use partioning. Whats happening is AccountNumber is being recycled in our sytem.I have a process that loads new accounts to this table. But if that account already exist (created few years back), this process wouldn't load thse
new accounts which is not what we want.
I am thinking of partiitoning this table based on year. But If I partition this table based on year,
how do I specify to not to look for previous year partion during the new account load; so that it will still get loaded? Can this be achived through partitioning?
May 24, 2013 at 3:48 am
Partitioning is the best one if you query the partitioned columns. But in your case you want to check accountnumber where as you partitioning would be based on Year. cant see it good one. In this case, you query will hit all partitions.
May 24, 2013 at 7:02 am
Can partitioning based on only one column? I am not concerned about query performance in this case. Moreover, archiving the data.
May 24, 2013 at 7:11 am
Partitioning does not disable your table integrity.
What you want is a cleaning/merge procedure that gets rids of old account number and insert new one, or even better, a real ETL process.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply