Can someone please provide a complete list of the circumstances under which SQL Compare forces a rebuild of a table?

For example, SQL Compare forces a rebuild if the target table has an identity field, but the source table does not.

Thank you.
crancoder
0

Comments

2 comments

  • Brian Donahue
    Hi,

    The list is available on our Knowledge Base already. SQL Compare rebuilds tables if one or more of the following is true:
    - Changing an IDENTITY seed or increment value or dropping the IDENTITY property from a column
    - Adding a column in the middle of a table when the 'force column order' option is enabled
    - When you add/alter/drop PERSISTED computed columns
    - When it is impossible to implicitly cast one data type to another (e.g. DECIMAL to NUMERIC)
    - Changing the filegroup specification for a table
    - Changing partitioned columns
    Brian Donahue
    0
  • crancoder
    Brian - Thanks!
    crancoder
    0

Add comment

Please sign in to leave a comment.