Best practice for data version control in sql and c# -


in question want figureout, best practice control versions of data in sql. useing relational database (sybase sap sql anywhere). problem is, don't know in layer of our software should implement version control system. want write generic system, version control available types of data small amout of work every type (types: contacts, appointments, ...).

here options figured out: 1. using entity framework , calculating difference of 2 models. saving difference database 2. using triggers , comapre old , new data , save them in separate table 3. using procedures proof changes , save them in separate table

i know it's general question, maybe 1 has idea , solution our problem.

edit

important: want create versions of data itself, not of sql schema or sql code.

edit2

lets use following simple example. have tiny contact table (not our real contact table):

create table contact (     "guid" uniqueidentifier not null unique,     "contactid" bigint not null identity(1,1),     "version" integer not null,     "firstname" varchar(100),     "lastname" varchar(200),     "address" varchar(400),     primary key (contactid, version) ); 

no, every time 1 made changes contact object, want save new version of it. im looking general solution. must implemented every type.

thank you!

as live , breathe database source control (part of amazing team @ dbmaestro), can recommend on combination of 2 methods, depending on how run delta.

  1. using triggers should save information need deployment, if using slow change dimension or entire table content
  2. using procedure analyze difference , knows generate relevant delta script

Comments

Popular posts from this blog

Java 3D LWJGL collision -

spring - SubProtocolWebSocketHandler - No handlers -

methods - python can't use function in submodule -