Help get this topic noticed by sharing it on Twitter, Facebook, or email.

When running DBAmp it removes any indexes and default values

When running DBAmp it removes all indexes and default values on my update/insert/delete tables. This severely slows down processing. How can this be avoided.
1 person has
this question
+1
Reply
  • Looking at these table properties this table was re-created at the time DBAmp 'Update:bulkapi' was executed but the default field values and indexes were not carried forward from the source table during DBAmp execution.

    Thinking there was a SS database issue, I re-applied all defaults and indexes just prior to DBAmp execution. These constraints are critical to the application.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited

  • The workflow of sf_bulkops is to write the row data and sf response to a new table (the _Result table) Then at the end of the process we drop the original table and rename the new table to the original name. This is done because it is much faster for use to bulk insert into the new table as opposed to update the original table row by row.

    I do not anticipate that we will change this workflow.

    Therefore the input tables to sf_bulkops should not be used as "storage" between sf_bulkop calls but rather as tables that are created just prior to the run. I would recommend that you alter your workflow to create the input table just prior to the sf_bulkops call by selecting the needed records from another table.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited