Re: Help on transactional replication



Thanks for the reply paul,
I have left the database/log size to autogrow and will keep an eye on
their size.

also, you haven't answered clearly whether am i doing a right thing by
keeping the distributor on a subscriber server instead of keeping it
with publisher in production server?

Could you also please indicate what sort of implication the production
server will have with this kind of setup? I have to make it clear to my
manager before i setup this thing on live environment.

And the basic question, I would think the initial snapshot should be
done out of business hours? If yes, how often i need to take the
snapshot or just reading the transaction logs would be enough as long
as there are no schema changes on the published tables?

Will the snapshot agent gets the entire shcema and data from the
published tables every time it runs or only at once in the begining in
transactional replication?

and the last thing, If you please don't mind can you show me some links
on how to read and understand processor and memory usage things.

Thanks very much

AK.

Paul Ibison wrote:
Firstly, the method you are following is fairly commonly used. The size of
the logs and databases depends entirely on your initial data size and
transaction volume, so as long as you have the logs set to a large size or
autogrow, you'll just have to monitor them for your circumstances. The
impact of replication on your system can be monitored using the normal
counters in windows system monitor (processor usage, ram usage and disk
usage - if you are not familiar with these I can dig out some links). To
prevent the use of the replication overhead in the event of a slowdown, you
could initially stop the log-reader agent then remove the publication.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

.

Relevant Pages

  • Re: SBS 2003 Premium R2 server becomes more unstable, page file gr
    ... and then when we took a look at the server, it appears as though the PF ... according to MS specs and your suggestion of the PF being 1.5x the RAM ... The VM Size is what seems to be getting large (Mem Useage ... Image Name Mem Usage VM Size ...
    (microsoft.public.windows.server.sbs)
  • Re: Extended Server Usage Report
    ... All I get is mofcomp usage statement after usage statement. ... Click Monitoring and Reporting. ... Step 3: Reinstall SBS Monitoring component ... Select Windows Small Business Server 2003 and then click Change/Remove. ...
    (microsoft.public.windows.server.sbs)
  • Re: Question about monitoring in SBS2K3 Prem. vs. SBS2K
    ... databases for analysis and report generation. ... Also new in the Windows Server 2003 family are two new security groups ... >Subject: Re: Question about monitoring in SBS2K3 Prem. ... >memory usage by percentage, processes that have been abnormally stopped, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Premium R2 server becomes more unstable, page file gr
    ... high CPU usage. ... The server hasn't crashed yet, but it has in the past. ... virtual memory or similar errors, I'd see if the instability is remedied, ... Image Name PID Username Session ID CPU Mem Usage Peak Mem Usage ...
    (microsoft.public.windows.server.sbs)
  • Re: High CPU usage in Exchange 2000
    ... But it's not the problem that 'System Idle ... Is it running on Window 2000 Standard or Advanced Server? ... relay, etc, and/or just not able to handle the user base and usage. ... but its highly informative showing you all Exchange and Windows ...
    (microsoft.public.exchange.setup)
Loading