Solved

Advice on SQL Server 2008 Replication

Posted on 2011-02-20
2
268 Views
Last Modified: 2012-05-11
Our company currently has a 6GB SQL Server database running on SQL Server 2008 R2 Enterprise, its a fair size as it stores various documents and files in tables using the IMAGE data type, we also store large amounts of text in tables using the NTEXT data type.  We currently have around 30 users on the network at our head office.  As a company we are now branching out and looking at setting up regional offices in the UK.  We anticipate having around 10 offices in total within 2-3 years.  At each branch office there will be around 4-5 users and will be connected to head office be way of a 1MB VPN.  Ideally we would like an SQL Server at each of the branch offices with a real-time copy of the database which can be updated from any location and all branches including head office are in sync with a full copy of the database.  I am currently setting up our first branch office and have implemented Transactional Replication with Updatable Subscriptions.  I am a newbie to SQL replication though and i am wondering whether or not i have chosen the right path to go down...  The problem i currently face is that an error is being displayed when trying to updated the database from the branch office, the data types IMAGE and NTEXT apparently cannot be used in this scenario.  I am wondering whether we should be using Merge Replcation instead or whether we need to move over to different data types.  Your help would be very much appreciated.
0
Comment
Question by:jambomambo
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 26

Accepted Solution

by:
tigin44 earned 500 total points
ID: 34937521
The architecture you are palnning will work.

You should change the data type image to varbinary and ntext to nvarchar(max).. Microsoft will not support that data types in the future.. Them are in sql 2008 only for the backward competibility reason.

0
 

Author Comment

by:jambomambo
ID: 34937963
Thanks for your response. Can you suggest the best way to convert the existing data types considering the replication has already been setup. Also would there been any data loss in the process?
0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This is basically a blog post I wrote recently. I've found that SARGability is poorly understood, and since many people don't read blogs, I figured I'd post it here as an article. SARGable is an adjective in SQL that means that an item can be fou…
There have been several questions about Large Transaction Log Files in SQL Server 2008, and how to get rid of them when disk space has become critical. This article will explain how to disable full recovery and implement simple recovery that carries…
In an interesting question (https://www.experts-exchange.com/questions/29008360/) here at Experts Exchange, a member asked how to split a single image into multiple images. The primary usage for this is to place many photographs on a flatbed scanner…
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question