I have a situation please suggest some transactional solution.

Question

hi,
    I have two databases one is entry database (DB1) Where entery is done, other database is reporting database (D2).
we are trying to transfer data using stored procedure from db1 to db2. the  sp will be scheduled to run after every 20 to 30 sec.
in db1 we keep three cols in all tables transferedcol, updatedcol, activecol.
--activecol gets 1 if when record is entered first time and remain same while updation.
this col gets 2 if deleted( we do not do physical deletion we only mark 2 in activecol and updagtedcol)
--transferedcol gets 1 if not transfered to db2, if transfered to db2 then we put 0 in it.
if record gets updated then it gets 1 again so that we can transfer it again.
--updatedcol gets 0 for new entry of  each record and 1 if updated after transfer of the record to db2 else if any one tries to updated it before transfer then it will be 0 for new record , after the transfer of that record if some one updates the record
then it gets 1 and remains 1 throught out the life . yes it gets 2 if record is deleted ( deletion is not  physical , it is logical by setting 2 in activecol and updatedcol).
in db2 we have only required cols for reporting,  but if required we can keep some cols like transfered ,active and updated.
this db2 has fk and table gets record from joins of many tables of db1 which also has  fks
that is schema is not same.
Q1) i want to transfer only the records having transfered col marked as 1 and after transfering i want to make them 0 from the stored procedure which runs after every 20 30 sec.
please suggest some solution with isolation level.
note: on db1 i want that entery should not be blocked to much and at the same it want stored procedure to transfer the data from db1 to db2 so that people can see the report at the very time.
yours sincerley

Answer 1

    I have two databases one is entry database (DB1) Where entery is done, other database is reporting database (D2).
we are trying to transfer data using stored procedure from db1 to db2. the  sp will be scheduled to run after every 20 to 30 sec.
Have you considered replication?
BOL: "SQL Server Replication
Replication is a set of technologies for copying and distributing data and database objects from one database to another and then synchronizing between databases to maintain consistency. Using replication, you can distribute data to different locations and
to remote or mobile users over local and wide area networks, dial-up connections, wireless connections, and the Internet.
Transactional replication is typically used in server-to-server scenarios that require high throughput, including: improving scalability and availability; data warehousing and reporting; integrating data from multiple sites; integrating heterogeneous data;
and offloading batch processing. Merge replication is primarily designed for mobile applications or distributed server applications that have possible data conflicts. Common scenarios include: exchanging data with mobile users; consumer point of sale (POS)
applications; and integration of data from multiple sites. Snapshot replication is used to provide the initial data set for transactional and merge replication; it can also be used when complete refreshes of data are appropriate. With these three types of
replication, SQL Server provides a powerful and flexible system for synchronizing data across your enterprise. Replication to SQLCE 3.5 and SQLCE 4.0 is supported on both Windows Server 2012 and Windows 8.
As an alternative to replication, you can synchronize databases by using Microsoft Sync Framework. Sync Framework includes components and an intuitive and flexible API that make it easy to synchronize among SQL Server, SQL Server Express, SQL Server Compact,
and SQL Azure databases. Sync Framework also includes classes that can be adapted to synchronize between a SQL Server database and any other database that is compatible with ADO.NET."
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014