Change primary key limitation for MS SQL Server sinks



1 comment

  • Official comment
    Geir Ove Grønmo

    The "sql" sink requires the table to have an immutable primary key in the entity that is reflected in the table. Using an auto incrementing column for primary key does not work as the sink is then not able to relate the entity. In general the sink need to have full control over the columns in the table – and no other process should be writing to it. A workaround might be to write into a separate table and then use triggers, or alternatively have a writable view on top of the existing table.

    If you have any ideas how to do this then consider implementing it as a microservice. This is a often asked question and people seem to have similar requirements, so there might others interested in such a microservice.

    Comment actions Permalink

Please sign in to leave a comment.