I'm importing an object which should replace a current object that holds millions of records, now my current object has new fields. And it's taking me hours and end up not being able to import the object at all. Has anyone encountered this? And what solution would you prefer.
Right now i'm exporting records through dataport and will delete them . And will be importing them back after redesigning
0
Comments
The thing is that sql alter the table, and then re-applying security fol all users. I had customer with huge DB and enhanced security model and had exactly the same issue. After we switched to standard security model - problem gone.
In fact, this is Ok, but you may need to wait hours and hours while object will be imported. On my 90Gb database it takes 7h to apply change to GL entry without new keys! Interestingly, the keys aren't affect import performance so much.
One time, i saw very bad primary key in table with 100.000 records, new fields added a very long time...
Next day actually I add secondary key and wait same time when I add simple field