When should data be decentralised? 1

[Stunner01225]

I have developed a new system that shares a common table with another. I want to make sure my system is independent so it will run faster and be more stable (and so I don’t have to rely entirely on another team). I am pretty sure using replication I can get up to date data. The problem is I need to convince management some I need a few more facts and to know of anything that could upset my plans. So.
When should data be decentralised? And are my opinions correct?
Reassurance very much welcome!
Cheers.

 

[JBaileys]

Stunner,


What are your stability concerns? Do you have concerns with people upsetting the data or data structures?

We developed a production system on the AS/400 and developed a data warehouse in sql server. Much of the finance users data requests come from sql server. It allows them to build reports and not affect the production as/400. Reasons to replicate data include performance. If a user develops a report that requests all data from all tables. It does not hurt the other system. In some cases, you may develop two very different data designs to support a system. Using replication the same data is used and managed and stored differently.

Be careful that there is only 1 version of the truth. Ideally, you would not allow users to make changes to the data in both places (if possible). It keeps things cleaner if replication goes one way. Maintaining a consistent source to destination replication.

 

[Stunner01225]

Thank you .
The data replication is one way as our system does not change or update it . It is used only for reference. The System is web based with an asp front end and SQL server backend.
Any over benefits other than speed and stability, and more over any downsides to my plan.
Cheers

 

[JBaileys]

The only major concern that I can see to your plan is volume. If the sql engine is getting a lot of hits - yea probably makes sense to replicate. Managements only concerns - what does it cost me for the new hardware / software and how much time will be required to manage to sets of data instead of 1.

If you need to "sell" management - provide them the options and show them there is limited or no risk by replicating the data. Another advantage comes down to disaster recovery. If one fails, you theoretically have a "mirrored backup" - otherwise you have to return to a back up or tape.

May suggest to management that you can build a dts job that very easily can rebuild the db in the eventof a failure.

 

[Stunner01225]

Thanks for all your help.