Is it possible to merge continuously between 8am and 5pm?

I have servers in a merge scenario that replicate every ten minutes. When
changes occur, they need to replicate fairly quickly (within 30 minutes),
but changes may not occur in every hour.
I think it would be most efficient to run continuous rather than every 10
minutes. However, I would really like replication to not be running at all
outside of the 8am-5pm window. Is it possible to have continuous
replication, but only from 8am to 5pm? The SQL Enterprise Manager does not
seem to allow for it.
Rob Kraft
Sure. Add a job that runs at 8AM and again at 5PM. What does this job do?
It changes the schedule on the replication job.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
sql

Is it possible to do Replication Manually

Hi,
This is a silmple Qn. I know it is possible to Replicate thru Query
Analizer. But i don't know the steps
can anyone help me
An
Have you looked at Log shipping? We use a home grown version for some of our
SQL servers, with out any problems.
"AR" <aneesh.r@.eostek.com> wrote in message
news:OZulCUc4EHA.1192@.tk2msftngp13.phx.gbl...
> Hi,
> This is a silmple Qn. I know it is possible to Replicate thru Query
> Analizer. But i don't know the steps
> can anyone help me
> An
>
sql

Is it possible replicate Service Broker Object and messages?

Could anybody suggest to me - is it possible replicate Service Broker Object and messages (in the queue) with usual Replication Process?

Thanks to all very much,

Sveta.

what are service broker object and messages, user tables? views? procs? if not, then no. if yes, and they're not marked as system objects, then you might be able to, just know that some replication topologies will add columns and indexes to tables.|||

Thank you for the explanation!

Sveta

is it good idea to replicate sql server db files?

Hi.

I am wondering if it is a good idea to replicate sql server db files
using frs.

I don't really know how the frs works, so
does frs replicates the whole database from time to time or just the
portion that is changed?

Also if the db is expected to change very often, and wouldn't it make
the whole system down?

I wonder if it's a good idea just to make a backup of the database and
copy it.

What's the usual practice?[posted and mailed, please reply in news]

jaekim (jkim65@.socal.rr.com) writes:
> I am wondering if it is a good idea to replicate sql server db files
> using frs.
> I don't really know how the frs works, so
> does frs replicates the whole database from time to time or just the
> portion that is changed?
> Also if the db is expected to change very often, and wouldn't it make
> the whole system down?
> I wonder if it's a good idea just to make a backup of the database and
> copy it.
> What's the usual practice?

I'm uncertain of what your question actually is, and whatever I have never
heard of frs.

You talk about replication, but your question seems to be about backup.
Replication and backup are two quite different things.

To backup a database, you use the BACKUP command in T-SQL. There are three
ways to back up a database:

* Full backup, backup the entire database.
* Differential backup, back up the changes since the last full backup.
* Log backup, backs up the *transaction log*.

Normally you use both Full backup and Log backup. By backing up the
transaction log, you can get up-to-the-minute recovery in case of a
crash (which could be a fatal human error).

To be able to backup the transaction log you must run in Full or Bulk-logged
recovery mode. On the other hand, if you run in these modes, you must
backup the transaction log, or the log will eventually fill your disk.

It is important to understand that SQL's BACKUP command knows about
transactions, and thus you can backup the database while there is
activity in it. If you would just copy the database files outside SQL
Server, you might get a useless set of bytes on the tape.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||"jaekim" <jkim65@.socal.rr.com> wrote in message
news:91d0d16b.0407040210.7116f55d@.posting.google.c om...
> Hi.
> I am wondering if it is a good idea to replicate sql server db files
> using frs.
> I don't really know how the frs works, so
> does frs replicates the whole database from time to time or just the
> portion that is changed?
> Also if the db is expected to change very often, and wouldn't it make
> the whole system down?
> I wonder if it's a good idea just to make a backup of the database and
> copy it.

I would NOT trust FRS to replicate my database.

Either as Erland suggests use BACKUP and RESTORE (look up log-shipping) or
use SQL Server's replication.

> What's the usual practice?|||On Sun, 4 Jul 2004 12:51:28 +0000 (UTC), Erland Sommarskog wrote:

> I'm uncertain of what your question actually is, and whatever I have never
> heard of frs.
> You talk about replication, but your question seems to be about backup.
> Replication and backup are two quite different things.
FRS refers to File Replication Service, provided by Windows 2000 Server and
Windows Server 2003. It basically does the same thing as rsync: copy file
changes from one server to another on a scheduled basis.

Some details:
http://www.microsoft.com/windows200...dh_frs_ncpi.asp

Your recommendations are of course correct: Database replication is best
handled by the database server, not the filesystem.

Is full-replication of *all* databases possible?

Hi All,
I am a newbie to MS SQL Server 2000 but I really need to solve this issue:
We need to daily replicate all databases within our MS SQL Server 2000 to
another MS SQL Server 2000 - the amount of databases is not fixed because
new databases are created on a daily basis.
--> Is it possible to create a job that replicates all databases from one MS
SQL Server to another and where do I have to configure it? (I already looked
at the abonnement- and replication-assistent in the enterprise manager but I
couldn't find any option to automatically daily replicate *all* databases..)
I hope somebody can help me! Any hints are highly appreciated.
cheers, jan
On Thu, 27 Oct 2005 17:26:25 +0200, "Jan Rsner" <jan.roesner@.web.de>
wrote:
>I am a newbie to MS SQL Server 2000 but I really need to solve this issue:
>We need to daily replicate all databases within our MS SQL Server 2000 to
>another MS SQL Server 2000 - the amount of databases is not fixed because
>new databases are created on a daily basis.
>--> Is it possible to create a job that replicates all databases from one MS
>SQL Server to another and where do I have to configure it? (I already looked
>at the abonnement- and replication-assistent in the enterprise manager but I
>couldn't find any option to automatically daily replicate *all* databases..)
>I hope somebody can help me! Any hints are highly appreciated.
If it's only "daily" you might just ship backups or something.
No, there's no way to automagically have a new database "replicate"
itself, some kind of setup is going to be required.
HTH,
J.