replication timeout

I have 3 production machines which are replicated to a dr site, all
machines are using a central distributor machine. I have created a
separate distributor database for each system.
My problem is that one of my systems will not replicate I am doing
snapshot and transactional, it just keeps timing out I have put sql
profiler on the dr box and can see that the data gets to the box but
it just times out. All boxes publisher, distributor, subscriber can
see each other so why is it timing out?
what is the exact error message you are getting?
"stephen" <twolf@.icon.co.za> wrote in message
news:75c81dee.0404170439.22bbd18d@.posting.google.c om...
> I have 3 production machines which are replicated to a dr site, all
> machines are using a central distributor machine. I have created a
> separate distributor database for each system.
> My problem is that one of my systems will not replicate I am doing
> snapshot and transactional, it just keeps timing out I have put sql
> profiler on the dr box and can see that the data gets to the box but
> it just times out. All boxes publisher, distributor, subscriber can
> see each other so why is it timing out?
|||Have you looked into creating a different snapshot profile?
If you go into Publisher/Distributor Properties, Agent Profiles, and
then Snapshot Tab, If you look at the existing "Default profile" the
Query time-out is set to 300; you might want to increase that number
to maybe 1000 or so.
Here is something that I have found interesting though that you might
want to know ahead of time so you DON'T CANCEL the replication
process:
Depending on how high you increase this number to, there is always the
potential of getting a somewhat bizare error message while the
replication is running stating that no response has been received from
the snapshot agent, and the Replication monitor will display the red X
symbols (like if it had failed). However, the process is still alive
and well (you can check it under jobs to see if it is still in fact
running), so once it goes past the table that may be causing it to
time-out, the Replication monitor will refresh and the Xs will be
removed.
Try this on a test environment first as every environment reacts
diferently, and always remember to keep a current backup just in case.
Hope this helps.
Jose
twolf@.icon.co.za (stephen) wrote in message news:<75c81dee.0404170439.22bbd18d@.posting.google. com>...
> I have 3 production machines which are replicated to a dr site, all
> machines are using a central distributor machine. I have created a
> separate distributor database for each system.
> My problem is that one of my systems will not replicate I am doing
> snapshot and transactional, it just keeps timing out I have put sql
> profiler on the dr box and can see that the data gets to the box but
> it just times out. All boxes publisher, distributor, subscriber can
> see each other so why is it timing out?

Replication Throughput

Hi everyone,
We have a SQL replication that moves a large amount of data between our
administration site and a production eCommerce platform at our hosting
provider. The hardware at either end isn't especially taxed on either the
source cluster or the destination cluster and bandwidth shouldn't be an issue
either as we have a 9Mbps pipe at HQ and the hosting provider has MUCH more
available.
The problem is that this synchronization job is taking a huge amount of time
as I see the replication traffic move at a rate of 25Kbps to 250Kbps.
Because of the locks that the import imposes, this has the effect of shutting
the site down.
I realize that this isn't the best designed site and that there are better
ways to do this, but we have inherited this site and have to keep it working
until the redesigned pieces can be moved into production... near the top of
the list is fixing this.
I am open to suggestions; please help.
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
Chicago, IL
Remember: Marking helpful answers helps everyone find the info they need
quickly.
Please take a look at this article for optimisation posibilities:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
HTH,
Paul Ibison

Replication Subscription Standard Edition

So I set up a "Replication/Local Publication" on a Production SQL
2005
Database.
It publishes a Database on the production database.
I then set up a "Replication/Local Subscription" on another Database
we call "Report Database"
that will have reports running on it and querying the Subscription
which is feed from the
production database.
They are syncronizing fine and everthing looks great.
My question is how do I access the Subscription? Can I query it like
a
database
using a "Database Engine Query"? Do I have to create a Database
instance on the "Report Database" Server
feeding off the Subscription?
Am I not going to be able to access the subscription because I don't
have snap shots?
I have no idea what to do now? How can I query the subscription? Can
the subscription act like a database?
I am having problems understanding the question. You have transactional
replication set up correctly and it is syncing ok to the Report Database.
This database can now be queried as per usual. if you are concerned about
blocking, you could use read_committed_snapshot isolation level to help with
the concurrency of reports.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Replication makes copies of tables and their data which by default will be
identical to the tables in the publication database. You should be able to
query them in the same way you query them in the publication database.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"jughead" <mike.aarset@.gmail.com> wrote in message
news:1173882913.696871.315700@.o5g2000hsb.googlegro ups.com...
> So I set up a "Replication/Local Publication" on a Production SQL
> 2005
> Database.
> It publishes a Database on the production database.
> I then set up a "Replication/Local Subscription" on another Database
> we call "Report Database"
> that will have reports running on it and querying the Subscription
> which is feed from the
> production database.
>
> They are syncronizing fine and everthing looks great.
>
> My question is how do I access the Subscription? Can I query it like
> a
> database
> using a "Database Engine Query"? Do I have to create a Database
> instance on the "Report Database" Server
> feeding off the Subscription?
> Am I not going to be able to access the subscription because I don't
> have snap shots?
>
> I have no idea what to do now? How can I query the subscription? Can
> the subscription act like a database?
>
|||On Mar 14, 8:12 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
> Replication makes copies of tables and their data which by default will be
> identical to the tables in the publication database. You should be able to
> query them in the same way you query them in the publication database.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
> "jughead" <mike.aar...@.gmail.com> wrote in message
> news:1173882913.696871.315700@.o5g2000hsb.googlegro ups.com...
>
>
>
>
> - Show quoted text -
I'm just wondering how to query the subscription.
When the subscription is created on the Report Database is a database
created on that server?
|||On Mar 14, 8:15 am, "jughead" <mike.aar...@.gmail.com> wrote:
> On Mar 14, 8:12 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
>
>
>
>
>
>
>
>
>
> I'm just wondering how to query the subscription.
> When the subscription is created on the Report Database is a database
> created on that server... Hide quoted text -
> - Show quoted text -
I had an existing database on my Report Server that was the same name
of the Database on the Production Server that is getting publicated.
I am going to do a new publication on a different database and see how
it goes. Thanks guys
|||No, its not, you have to pre-create it.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"jughead" <mike.aarset@.gmail.com> wrote in message
news:1173885320.499067.58050@.y66g2000hsf.googlegro ups.com...
> On Mar 14, 8:12 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
> I'm just wondering how to query the subscription.
> When the subscription is created on the Report Database is a database
> created on that server?
>
|||On Mar 14, 10:58 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
> No, its not, you have to pre-create it.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
> "jughead" <mike.aar...@.gmail.com> wrote in message
> news:1173885320.499067.58050@.y66g2000hsf.googlegro ups.com...
>
>
>
>
>
>
>
>
> - Show quoted text -
You guys are right. I don't know what the heck I was doing when I
created my first Publication and Subscription.
Seems that everything is awesome now!
Thanks everyone
sql

Replication Question

I have continuous transactional replication running from a production server to a reporting server. Both servers are SQL 2000. A week or so ago, a new column was added to a table being replicated, both production and reporting servers. I need to get that field included in the replication. Can this be done without having to drop the subscription, adding the field, re-create the subscription and then re-creating a snapshot?Go to BOL. Look up sp_repladdcolumn. Here is part of what it says:



sp_repladdcolumn
Adds a column to an existing table article that has been published. Allows the new column to be added to all publishers that publish this table, or just add the column to a specific publication that publishes the table. This stored procedure is executed at the Publisher on the publication database.|||Thank you!

Replication Question

Hello
I have a production database that i would like to have mirrored on another
server. I have never worked with database replication, but from what I
understand, changes made to any of the replicated DBs get reflected in all
other DBs. What I need is to have the one production database copied daily
(or weekly) to another box.
Can I somehow set this up through replication so that the replicated
database cannot be updated? ie is static and just syncs to the production db?
Should I be using replication or another tool/process?
Thanks for the help!
Ben,
log-shipping would almost certainly be more suitable for these requirements.
Please take a look at this article:
http://www.replicationanswers.com/Standby.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Depending on the size of your db and transaction logs, either restore the
entire database each time, or as Paul has mentioned use Log Shipping.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ORqmG4IOGHA.2268@.TK2MSFTNGP09.phx.gbl...
> Ben,
> log-shipping would almost certainly be more suitable for these
> requirements. Please take a look at this article:
> http://www.replicationanswers.com/Standby.asp
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>

Replication Question

I have continuous transactional replication running from a production server
to a reporting server. Both servers are SQL 2000. A week or so ago, a new
column was added to a table being replicated (on both production and
reporting servers). I need to get that field included in the replication.
Can this be done without having to drop the subscription, adding the field,
re-create the subscription and then re-creating a snapshot?
Message posted via http://www.droptable.com"cynault via droptable.com" <u7602@.uwe> wrote in message
news:61851d6b86210@.uwe...
> I have continuous transactional replication running from a production
server
> to a reporting server. Both servers are SQL 2000. A week or so ago, a
new
> column was added to a table being replicated (on both production and
> reporting servers). I need to get that field included in the replication.
> Can this be done without having to drop the subscription, adding the
field,
> re-create the subscription and then re-creating a snapshot?
>
Not if the column has already been added.
But look up sp_repladdcolumn for future reference.

> --
> Message posted via http://www.droptable.com|||Thank you!
Message posted via http://www.droptable.com|||Thank you!
Message posted via http://www.droptable.com

Replication Question

I have continuous transactional replication running from a production server
to a reporting server. Both servers are SQL 2000. A week or so ago, a new
column was added to a table being replicated (on both production and
reporting servers). I need to get that field included in the replication.
Can this be done without having to drop the subscription, adding the field,
re-create the subscription and then re-creating a snapshot?
--
Message posted via http://www.sqlmonster.com"cynault via SQLMonster.com" <u7602@.uwe> wrote in message
news:61851d6b86210@.uwe...
> I have continuous transactional replication running from a production
server
> to a reporting server. Both servers are SQL 2000. A week or so ago, a
new
> column was added to a table being replicated (on both production and
> reporting servers). I need to get that field included in the replication.
> Can this be done without having to drop the subscription, adding the
field,
> re-create the subscription and then re-creating a snapshot?
>
Not if the column has already been added.
But look up sp_repladdcolumn for future reference.
> --
> Message posted via http://www.sqlmonster.com|||Thank you!
--
Message posted via http://www.sqlmonster.comsql

Replication problem in SQL Server 2000

Hi all SQL Server experts!

I have created replication on my two servers (production and backup servers). I used wizards to create it and then generated SQL script for deleting and creating replication. For another task I came across the command sp_removedbreplication 'dbname' and I tried to use that for removing replication more easily on the servers. It seemed to not remove everything on the production server and whenever I install replication now, either by using wizards or my generated SQL scripts I get an error icon (red circle with a black X in it) on my Replication Monitor all the way down to Publisher and the publication named with the computer name. Also this icon is on Agents and Log Reader Agents but not on the actual agent.

Something must have happened when using sp_removedbreplication 'dbname' and I can't fix it. The replication works properly but i wish to not have the error icons.

Does anyone know how the error icons can be removed?

Best,
/M

The cleanest way and supported way is to drop the distributor and recreate it from scratch. However you can also look at the following tables in distribution database and delete any rows that reference your deleted publications (but take a backup of the distribution database first, and note that manually deleting these tables is unsupported):

MSpublications

MSsubscriptions

MSarticles

|||

I have checked these tables and they don't have anything that don't exist in them.

I have also dropped everything that has to do with replication and also the distribution database to use my scripts and install replication again. The replication works fines but there are still error icons on the folders. Only on the folders though and not on the actual items, e.g. agents. I am thinking of reinstalling the SQL Server. Might it be because SQL Server has replaced the actual icons with error icons and "lost" the orignial ones?

My scripts for installing replication has always worked but it is after I have used sp_removedbreplication on the distributor/publisher that these icons occur when I install replication, including using the wizards.

Best,
/M

|||Did you try disconnecting from the distributor and reconnecting to it. Sometimes the refresh of the data can cause such misbehavior. Also try restarting the sql server.|||

When deleting subscription, it's replication job may still remain. You can find it in SQL Server Agent Jobs list (in Enterprise Manager: [DB]->Management->SQL Server Agent->Jobs).

Name of the job consists of Publisher and Subscriber names. When you re-create a subscription, probably same name is generated, and job creation fails.

Use sp_delete_job stored procedure to delete the job.

|||

Thank you very much. That solved my problem.

Best,
/M

Replication problem in SQL Server 2000

Hi all SQL Server experts!

I have created replication on my two servers (production and backup servers). I used wizards to create it and then generated SQL script for deleting and creating replication. For another task I came across the command sp_removedbreplication 'dbname' and I tried to use that for removing replication more easily on the servers. It seemed to not remove everything on the production server and whenever I install replication now, either by using wizards or my generated SQL scripts I get an error icon (red circle with a black X in it) on my Replication Monitor all the way down to Publisher and the publication named with the computer name. Also this icon is on Agents and Log Reader Agents but not on the actual agent.

Something must have happened when using sp_removedbreplication 'dbname' and I can't fix it. The replication works properly but i wish to not have the error icons.

Does anyone know how the error icons can be removed?

Best,
/M

The cleanest way and supported way is to drop the distributor and recreate it from scratch. However you can also look at the following tables in distribution database and delete any rows that reference your deleted publications (but take a backup of the distribution database first, and note that manually deleting these tables is unsupported):

MSpublications

MSsubscriptions

MSarticles

|||

I have checked these tables and they don't have anything that don't exist in them.

I have also dropped everything that has to do with replication and also the distribution database to use my scripts and install replication again. The replication works fines but there are still error icons on the folders. Only on the folders though and not on the actual items, e.g. agents. I am thinking of reinstalling the SQL Server. Might it be because SQL Server has replaced the actual icons with error icons and "lost" the orignial ones?

My scripts for installing replication has always worked but it is after I have used sp_removedbreplication on the distributor/publisher that these icons occur when I install replication, including using the wizards.

Best,
/M

|||Did you try disconnecting from the distributor and reconnecting to it. Sometimes the refresh of the data can cause such misbehavior. Also try restarting the sql server.|||

When deleting subscription, it's replication job may still remain. You can find it in SQL Server Agent Jobs list (in Enterprise Manager: [DB]->Management->SQL Server Agent->Jobs).

Name of the job consists of Publisher and Subscriber names. When you re-create a subscription, probably same name is generated, and job creation fails.

Use sp_delete_job stored procedure to delete the job.

|||

Thank you very much. That solved my problem.

Best,
/M

Replication PK/FK conflict

We have established a Report server (subscriber) for our
OLTP production database (publisher). Transaction
replication is running between the two databases.
An UPDATE on the OLTP database is triggering a
DELETE/INSERT on the Report database. This DELETE is
causing a FK conflict and results in replication errors.
It appears that if an UPDATE is done on an index key, this
causes a DELETE/INSERT instead of an UPDATE. Is there any
way to handle this without dropping the FKs on the Report
(subscriber) database in replication?
Thanks
Jay,
this is a known issue. There is a solution though:
http://support.microsoft.com/default...NoWebContent=1
hth,
Paul

Replication over Dev Server

I got 2 servers running, Dev and Production
The Production one is the one that the users run on and it's working
with a Access adp project
The Dev one is the migration project that evolve and use VB as
interface.
So my test are made on the Dev version but, the way it work now is i
copy my database files and trasnfert it to my dev server, delete my
current database and relink new files and start working again. Im
doing so for a while now and it become pretty long to do with size
increment. So i think it's time to change to automatic process. I've
tried with DTS packages but DTS transform view into table and don't
transfer everything. So Replication seems the best thing. I need to
know if the current thing his possible and if it is, is there good
tutorial for such replication i could use ?
i would like to replicate my Prod server to Dev each morning and i
don't want Dev modification to propagate to Prod. so make a kind of
backup database in other word.
I would say that your current method is possibly the best. You could use
snapshot replication as an alternative, but if you want the whole database
and are already backing it up, it might be simpler to ship the backups and
restore on the DEV server. If you are going across the network and this is
slow, then you could investigate zipping and unzipping before the file
transfer. I have a similar setup, and even though it isn't out of the box, it
works well.
HTH,
Paul Ibison
|||On Apr 24, 4:28 am, Paul Ibison <Paul.Ibi...@.Pygmalion.Com> wrote:
> I would say that your current method is possibly the best. You could use
> snapshot replication as an alternative, but if you want the whole database
> and are already backing it up, it might be simpler to ship the backups and
> restore on the DEV server. If you are going across the network and this is
> slow, then you could investigate zipping and unzipping before the file
> transfer. I have a similar setup, and even though it isn't out of the box, it
> works well.
> HTH,
> Paul Ibison
Ill this this this morning and see how it goes. should be fast under
1gbit lan.
|||On Apr 24, 8:20 am, Franck <the_darkbl...@.hotmail.com> wrote:
> On Apr 24, 4:28 am, Paul Ibison <Paul.Ibi...@.Pygmalion.Com> wrote:
>
> Ill this this this morning and see how it goes. should be fast under
> 1gbit lan.
i manage a vb script that backup with t-sql the Prod server and after
does a little DOS copy command to the Dev server and T-sql again the
Restore, all that take only 35-40 seconds. restore being the longest
step.

Replication on MSDE2000 and db size problem

Hi,
We have following scenario:
2 PC on WinXP + MSDE2000 + SP4 with production db. Secondary PC works as
failover backup. DBs are connected by merge replication where backup is as
subscriber.
The problem is related to one table with binary column (2K) and its growing
size (over 100MB per day).
sp_spaceused product_map
name rows reserved data index_size unused
Product_map 24238 1056648KB 130448KB 13520KB 912640KB
It seems that on insert rows server allocates more space than need. This
problem occures only when system works on publisher db. It is ok when I
switch it to backup PC.
I have the same systems on W2k + MSDE2000 + SP3a + merge replication and
don't observe the problem like this.
could you help me how to diagnose it more deeply and solve the problem?
Janek
A couple of points 1) are you using text in row?
2) Are you sure the data in this column is the same on the publisher and
subscriber. Depending on how you update your text or image data it may not
be replicated.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Janek" <Janek@.discussions.microsoft.com> wrote in message
news:456DC0D6-FEDC-43BF-8A22-B6CE22069464@.microsoft.com...
> Hi,
> We have following scenario:
> 2 PC on WinXP + MSDE2000 + SP4 with production db. Secondary PC works as
> failover backup. DBs are connected by merge replication where backup is as
> subscriber.
> The problem is related to one table with binary column (2K) and its
> growing
> size (over 100MB per day).
> sp_spaceused product_map
> name rows reserved data index_size
> unused
> Product_map 24238 1056648KB 130448KB 13520KB 912640KB
> It seems that on insert rows server allocates more space than need. This
> problem occures only when system works on publisher db. It is ok when I
> switch it to backup PC.
> I have the same systems on W2k + MSDE2000 + SP3a + merge replication and
> don't observe the problem like this.
> could you help me how to diagnose it more deeply and solve the problem?
> Janek
|||1) data type for table is: int, smallint, int, char(11), smallint, smallint,
binary(2001), bit, datetime, int
2) All data is replicating, I can see it on reports on each machines. From
sp_spaceused report I see almost 1GB of unused space.
I know only one workaround:
dbcc dbreindex (.... + shrink db - a few cycles makes db to similar
backup db size.
At the moment system is working on backup PC without problem and new data is
refreshed to publisher.
Janek
"Hilary Cotter" wrote:

> A couple of points 1) are you using text in row?
> 2) Are you sure the data in this column is the same on the publisher and
> subscriber. Depending on how you update your text or image data it may not
> be replicated.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Janek" <Janek@.discussions.microsoft.com> wrote in message
> news:456DC0D6-FEDC-43BF-8A22-B6CE22069464@.microsoft.com...
>
>

Replication of a large database

Hi, all!
I will greatly appreciate if you share your experience of the replication of
large database.
Our production database is over 100 GB. There is transactional replication
of all the tables of the database to another server. The replicated database
on the subscriber is used as failover and for running reports. We run almost
24x7 environment.
There are some database schema changes coming with a new application version
which cause dropping and recreating the publication.
1.Can transactional replication of the large database be settled completely
online with the concurrent snapshot option? Will it cause great amount of
transactions waiting to be delivered? The production database is heavily used.
2.Last time the initial synchronization was running 8 hours. No sync
initialization could be a solution but I found information that it raises
errors creating stored procedures on the subscriber with SP4, and I have SP3
on the publisher and SP4 on the subscriber. Is it better idea to divide
publication of the large database logically in several smaller articles?
3.Because the database is large, I am going to implement partitioning using
partitioned views for historical data archiving. Do you know some tips
concerning transactional replication of partitioned views?
1) Yes it can be done, but I would not recommend it. I would try a backup
restore with a no sync option. Then you have to fix all triggers,
constraints, identity columns, etc.
2) Can you elaborate on this problem? I have not run into it.
3) Indexed Views can be replicated as views or tables. DPV's would typically
reside on your main server. To get them to work correctly you must implement
check constraints, so you would have to make sure that the check constraints
were applied on the subscriber(s).
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Elena" <Elena@.discussions.microsoft.com> wrote in message
news:DC26B8CB-34EB-4FCC-A258-DCD7D3064EF7@.microsoft.com...
> Hi, all!
> I will greatly appreciate if you share your experience of the replication
of
> large database.
> Our production database is over 100 GB. There is transactional replication
> of all the tables of the database to another server. The replicated
database
> on the subscriber is used as failover and for running reports. We run
almost
> 24x7 environment.
> There are some database schema changes coming with a new application
version
> which cause dropping and recreating the publication.
> 1.Can transactional replication of the large database be settled
completely
> online with the concurrent snapshot option? Will it cause great amount of
> transactions waiting to be delivered? The production database is heavily
used.
> 2.Last time the initial synchronization was running 8 hours. No sync
> initialization could be a solution but I found information that it raises
> errors creating stored procedures on the subscriber with SP4, and I have
SP3
> on the publisher and SP4 on the subscriber. Is it better idea to divide
> publication of the large database logically in several smaller articles?
> 3.Because the database is large, I am going to implement partitioning
using
> partitioned views for historical data archiving. Do you know some tips
> concerning transactional replication of partitioned views?
|||Thanks for reply, Hilary
2) I am afraid that No sync initialization can cause more problems which can
take longer time to fix
(http://support.microsoft.com/default...b;en-us;827175) than just
initial syncronization.
Also I wonderif it is reasonable to create several small publications on the
logical basis instead of creating one publication of all the tables of the
database. And then if necessary recreate small publication if database schema
changes.
"Hilary Cotter" wrote:

> 1) Yes it can be done, but I would not recommend it. I would try a backup
> restore with a no sync option. Then you have to fix all triggers,
> constraints, identity columns, etc.
> 2) Can you elaborate on this problem? I have not run into it.
> 3) Indexed Views can be replicated as views or tables. DPV's would typically
> reside on your main server. To get them to work correctly you must implement
> check constraints, so you would have to make sure that the check constraints
> were applied on the subscriber(s).
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Elena" <Elena@.discussions.microsoft.com> wrote in message
> news:DC26B8CB-34EB-4FCC-A258-DCD7D3064EF7@.microsoft.com...
> of
> database
> almost
> version
> completely
> used.
> SP3
> using
>
>

Replication Monitoring

What would be a best practice for monitoring Replication?
I have Transactional Replication going from the Production database (SQL00) to the Reporting database (SQL03).
Are there some Alerts I need to make sure I have setup to notify me?
Should I do a Validate Subscription once a week or so?
What would you do to have peace of mind that your reporting database is exactly in sync with your production database?
Thanx!
This depends on the stability of your links. If you are well connected, i.e. have highly reliable links set up the replication alerts to alert you when your job fails.
If your links are somewhat unstable set up the replication alerts to alert you when a job fails, but make sure you click on the response tab, and set a threshold to be alerted at, i.e. once per day, hour, etc.
You can schedule validations using sp_publication_validation. Use this proc in conjunction with the Replication: Subscriber has failed data validation alert.
How frequently you wish to run a validation depends on what you are doing. In general with a read only subscriber I never feel the need to run one. Your comfort level (or your bosses') might vary from mine.
With an updateable subscriber (immediate, queued, or merge) you might feel the need to run validations more often.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23juwUyqjEHA.2764@.TK2MSFTNGP11.phx.gbl...
What would be a best practice for monitoring Replication?
I have Transactional Replication going from the Production database (SQL00) to the Reporting database (SQL03).
Are there some Alerts I need to make sure I have setup to notify me?
Should I do a Validate Subscription once a week or so?
What would you do to have peace of mind that your reporting database is exactly in sync with your production database?
Thanx!