SQL Server Performance Forum – Threads Archive
To replicate or not to replicate?Hi I’m currently trying to decide whether to replicate a database or not. At the moment we only have the one SQL server in location A. Users in location B access data over a network to the SQL server on loctaion A but this is not very fast. One options is obviously replicating the database but this would mean having to get a SQL server in locationB. What type of licence would be required for the SQL server if i only want the replicated SQL server to be read only by about 3-4 uses? The biggest issue in deciding whether to replicate data is the cost – is it costly to set up?
I know that replication is an in depth subject and i have not looked at it at all even though i have been on the MS2073 course for programming SQL server 2000. Would you recommend attending a course to learn how to replicate ‘properly’ or is it fairly easy to follow by using the wizard etc? Thanks CE
If the users on location B is only wanted to query the SQL Server then why not take advantage of Log shipping, where the standby serve will be used for reporting purposes. Check this website for Log shipping article written by Brad. Books online is the best and first resource for information on unknown topic in SQL server, for further information on replication on web refer:
http://www.devarticles.com/c/a/SQL-Server/Replication-SQL-Server-2000-Part-2/ HTH Satya SKJ
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.
Could you just present the data to the users in location B with a web server and limit the recordsets to just what they really need to use?? That would be the quickest as you could have the data never leave location A. Otherwise, any solution you put in place is going to choke up on your network that’s "not very fast". That might end up being an issue anyway. MeanOldDBA
[email protected] When life gives you a lemon, fire the DBA.