Replicating a SQL Server database for read access -
i have application in production own database more 10 years.
i'm developing new application (kind of reporting application) needs read access database.
in order not linked database , able use newer dal (entity framework 6 code first) decided start new empty database, , added tables , columns need (different names production one).
now need way update new database production database regularly (would best if -almost- immediate).
i hesitated ask question on http://dba.stackexchange.com i'm not limited using sql server job (i can develop , run custom application if needed).
i made searches , had (part-of) solutions :
using transactional replication create smaller database (with tables/columns need). far can see, fact have different table names / columns names problematic. can use create smaller database automatically replicated sql server, still need replicate database new 1 (it may avoid production database stressed?)
using triggers insert/update/delete rows
creating custom job (either sql job or windows service runs every x minutes) updates necessary tables (i have lasteditdate updated trigger on tables, can know row has been updated since last replication)
do advice or maybe other solutions didn't foresee?
thanks
i think transactional replication better using triggers. resources used in source server/database due trigger fires each dml transaction.
transactional rep scheduled sql job , run few times day/night or part of nightly scheduled job. depends on how busy source db is...
there 1 more thing try - db mirroring. depends on sql server version.
Comments
Post a Comment