import/redesign of table

GilGil Member Posts: 49
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

Comments

  • pawanppawanp Member Posts: 90
    While importing table objects choose action Merge: Existing<-New or Merge: New<-Existing whichever is applicable.
  • GilGil Member Posts: 49
    Hi what are your experiences on this? So far after adding 3 Fields and some code to a header line with millions of records after hours of waiting its still not finish. Anyway i'll try this later on. Thanks
  • ppavukppavuk Member Posts: 334
    Are you using enhanced security model?
  • GilGil Member Posts: 49
    Yes we are using enhanced security model.
  • ppavukppavuk Member Posts: 334
    It why it takes so long.
  • GilGil Member Posts: 49
    Does anyone have any other ideas for this,though i haven't tried pawanp's solution yet. But i did test it on a database which has hundred thousands of record.
  • pawanppawanp Member Posts: 90
    If your new table object contains additional keys it will create SQL indexes. Considering you have millions of records you have to sit back and relax. Or consider disabling MaintainSQLIndex for those new keys, but depending on how important those keys are for you.
  • ppavukppavuk Member Posts: 334
    No, there no keys as i understand.

    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.
  • KeeperRUKeeperRU Member Posts: 58
    Bad keys actually very slow down changes to the tables.
    One time, i saw very bad primary key in table with 100.000 records, new fields added a very long time...
  • ppavukppavuk Member Posts: 334
    In this particular case they not changing a key, just adding a fields.
  • KeeperRUKeeperRU Member Posts: 58
    I'm too just added the fields (no keys wete touched that day :D )
    Next day actually I add secondary key and wait same time when I add simple field
  • GilGil Member Posts: 49
    Thank you for the replies, also i forgot to mention since a workmate of mine added also a key to this object while i added 3 fields. To be exact the current database is 800 GB and the current table i'm importing to has 111 million records(rows). This is making me crazy because of pressure from everyone else.
  • ppavukppavuk Member Posts: 334
    800 Gigs? It's massive! Never had so big ones :)
Sign In or Register to comment.