Groups | Blog | Home
all groups > sql server (microsoft) > may 2007 >

sql server (microsoft) : Replication controls (for an SQL newbie)


John F Kappler
5/25/2007 12:00:00 AM
Can someone point me at a website that might help me understand about
replication and its parameters (e.g. jobs and schedules).

We have SQL2005 on an SBServer 2003.

We have a third-party database application that lives on the server.

We also have four notebooks that keep copies of the application
database and the third-party supplier setup replication to keep the
databases synch'd whenever the notebooks are in the office.

(However, support from the third-party is intermittent and individuals
keep changing.).

The problem we're have is that intermittently, Notebook users find
their systems brough to a standstill by the task sqlserver which uses
all their processor resources. Sometime this only last for a few
minutes, sometimes for a couple of hours!

I've been asked to try and resolve this, but although I'm familiar
with databases I'm really a beginner with regard to SQL. I'm finding
it very diffiult to relate the various statuses, jobs, schedules,
replication tasks to each other and wondered if there is a tutorial
somewhere?

The notebooks each run SQLExpress, and we use SQL Server Management
Studio.

TIA,

JPhelpstead NO[at]SPAM gmail.com
6/7/2007 8:09:12 AM
[quoted text, click to view]

Hi John,

The best advice I could give to a SQL Server beginner is to make Books
Online your first port of call. It really is a very good source of
information and covers all aspects of replication very well.

If you search for replication you get a whole raft of info and if you
need something more specific i'm sure it will be there.

As for your specific problem, I would hazard a guess that this is
possibly due to the length of time left between the synching of the
data to your laptops. Obviously greater lengths of time will cause a
greater amount of data to be copied. I'm also not sure that SQL
Express is as well optimised as the larger flavours of SQL Server.
Maybe it would be worth investing in a second off-site server to
handle the replication, it is quite an intensive process?

Thanks
James

Senior SQL Server Developer
AddThis Social Bookmark Button