Replication Subscription Error

Hi,
I tried setting a server up as the publisher, distributor and subscriber.
When I tried to create either a push or pull subscription I got the following
message:
Error 14053: Cannot load the DLL replincrementlsn extended procedure, or one
of the DLLs it references. Reason: 126(error not found).
The subscription could not be updated at this time.
The subscription could not be created.
SQL Server Enterprise Manager could not create a pull subscription to
publication XXXX
Error 14053: Cannot load the DLL replincrementlsn extended procedure, or one
of the DLLs it references. Reason: 126(error not found).
The subscription could not be updated at this time.
The subscription could not be created.
Has anyone seen this before?
Server running SQL 2000 on Windows 2000 Server
Thanks
Something is not installed correctly. Reapply your latest service pack.
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
"DavidW" <DavidW@.discussions.microsoft.com> wrote in message
news:895B9996-9D97-4CAA-84F2-FF314F842E6F@.microsoft.com...
> Hi,
> I tried setting a server up as the publisher, distributor and subscriber.
> When I tried to create either a push or pull subscription I got the
> following
> message:
> Error 14053: Cannot load the DLL replincrementlsn extended procedure, or
> one
> of the DLLs it references. Reason: 126(error not found).
> The subscription could not be updated at this time.
> The subscription could not be created.
> SQL Server Enterprise Manager could not create a pull subscription to
> publication XXXX
> Error 14053: Cannot load the DLL replincrementlsn extended procedure, or
> one
> of the DLLs it references. Reason: 126(error not found).
> The subscription could not be updated at this time.
> The subscription could not be created.
> Has anyone seen this before?
> Server running SQL 2000 on Windows 2000 Server
> Thanks
>
|||Thank you Hilary, that has resolved the problem!
"Hilary Cotter" wrote:

> Something is not installed correctly. Reapply your latest service pack.
> --
> 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
> "DavidW" <DavidW@.discussions.microsoft.com> wrote in message
> news:895B9996-9D97-4CAA-84F2-FF314F842E6F@.microsoft.com...
>
>

Replication says success, but tables not showing in EM?

Hello All,
I am trying to replicate data from a SQL Server (7.0) to another SQL
Server using a one-way immediate push subscription. After executing,
there are no errors in the Snapshot or Push agents, but two of the
tables are missing in the subscription database. Where did they go?
I can find the tables listed in the publication->articles tab and in
the snapshot logs on the publisher. The tables are also listed on the
subscriber database under 'Database Roles Properties' --> Permissions.
Thank You For Your Time And Help,
Nate
Hi Nate,
You may want to check whether subscriptions for the two missing tables were
really created by calling sp_helpsubscription at the publisher. If not,
manually add them by calling sp_addsubscriptions with explicit article names
and rerun snapshot + distribution agents.
-Raymond
"Nate" <nathandeneau@.braintrade.biz> wrote in message
news:1142037215.646558.84890@.i40g2000cwc.googlegro ups.com...
> Hello All,
> I am trying to replicate data from a SQL Server (7.0) to another SQL
> Server using a one-way immediate push subscription. After executing,
> there are no errors in the Snapshot or Push agents, but two of the
> tables are missing in the subscription database. Where did they go?
>
> I can find the tables listed in the publication->articles tab and in
> the snapshot logs on the publisher. The tables are also listed on the
> subscriber database under 'Database Roles Properties' --> Permissions.
>
> Thank You For Your Time And Help,
> Nate
>
|||Everything looks as it should after calling sp_helpsubscription - the
two tables are listed.
|||This looks really strange. If you check the history messages of the snapshot
agent, do you see files for the two missing tables generated? And if you
check the distribution agent history, do you see that the files for the two
missing tables applied? If the tables are relatively small, you may be able
to fix things up by reinitializing the subscription, regenerate the snapshot
and reapply it. You may also want to watch out for processes outside of
replication that may have dropped the tables at the subscriber. What are the
sync_type values of subscriptions to the missing tables?
-Raymond
sql

Replication Question

I set up a transactional push replication and basically
would like to use the subscriber as the archived
historical database server.
Once the snapshot is completed, I would like to delete
old records on the publisher article and not replicate
the deletion onto the archive database
server. How do you do this once the replication is set
between the publisher and subscriber?
TIA.
Thank you.
>--Original Message--
>On the article properties for the particular table(s)
you
>want to stop the deletes, on the commands tab write NONE
>for the propagation of delete commands.
>Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>.
>

Replication problems

I am trying to get replication to work on my system and keep getting the
following problem trying to start up the Push to my servers.
All the schemas seem to be generated on all the servers, but not the tables.
After telling it to initialize the subscriptions I get the following
message:
***********************************************************************
Subscriptions were created successfully at the following Subscribers:
PTERADON
SQL Server Enterprise Manager could not start the service
'SQLServerAgent' on server 'DINO'.
5 - (Access is denied)
The subscription at Subscriber 'PTERADON' cannot be initialized
immediately because the snapshot for this publication is not yet
available. To initialize the subscription, start the Distribution Agent
after the snapshot is available.
***************************************************************************
SQLServerAgent is running on the Server "Dino", so I don't know why I am
getting that message.
Also, in the Replication Monitor, almost all the folders have a red
circle with an X in it.
In the "Snapshot agent" folder I have an item "northwind" (which is what
I am trying to publish), with the following message:
The process could not bulk copy out of table
'[dbo].[syncobj_0x4630333239354338]'.
In the "log reader agents", I get the following:
The license for this installation of SQL Server does not permit Log
Reader Agent to run at the Publisher.
Could not get license information correctly.
I also get the License message for the distribution agents.
What License are they talking about?
Thanks,
Tom.Is your sql service running as user with administrative rights or is it
running as local system. Try to use user with admin rights.
"Thomas Scheiderich" <tfs@.deltanet.com> wrote in message
news:3FC462B7.6080805@.deltanet.com...
> I am trying to get replication to work on my system and keep getting the
> following problem trying to start up the Push to my servers.
> All the schemas seem to be generated on all the servers, but not the
tables.
> After telling it to initialize the subscriptions I get the following
> message:
> ***********************************************************************
> Subscriptions were created successfully at the following Subscribers:
> PTERADON
> SQL Server Enterprise Manager could not start the service
> 'SQLServerAgent' on server 'DINO'.
> 5 - (Access is denied)
> The subscription at Subscriber 'PTERADON' cannot be initialized
> immediately because the snapshot for this publication is not yet
> available. To initialize the subscription, start the Distribution Agent
> after the snapshot is available.
>
***************************************************************************
> SQLServerAgent is running on the Server "Dino", so I don't know why I am
> getting that message.
> Also, in the Replication Monitor, almost all the folders have a red
> circle with an X in it.
> In the "Snapshot agent" folder I have an item "northwind" (which is what
> I am trying to publish), with the following message:
> The process could not bulk copy out of table
> '[dbo].[syncobj_0x4630333239354338]'.
> In the "log reader agents", I get the following:
> The license for this installation of SQL Server does not permit Log
> Reader Agent to run at the Publisher.
> Could not get license information correctly.
> I also get the License message for the distribution agents.
> What License are they talking about?
> Thanks,
> Tom.
>|||Dalibor Cvijetinovic wrote:
> Is your sql service running as user with administrative rights or is it
> running as local system. Try to use user with admin rights.
>
No. I have both set up as SqlAgentCmdExec and it has executive priviledges.
All the tasks have these license errors as shown below and may be why I
can't get this to work correctly.
Where do they come from and why am I getting them. Did I not load
something correctly when I set up Sql Server 7'
Thanks,
Tom.
>
> "Thomas Scheiderich" <tfs@.deltanet.com> wrote in message
> news:3FC462B7.6080805@.deltanet.com...
>>I am trying to get replication to work on my system and keep getting the
>>following problem trying to start up the Push to my servers.
>>All the schemas seem to be generated on all the servers, but not the
> tables.
>>After telling it to initialize the subscriptions I get the following
>>message:
>>***********************************************************************
>>Subscriptions were created successfully at the following Subscribers:
>>PTERADON
>>SQL Server Enterprise Manager could not start the service
>>'SQLServerAgent' on server 'DINO'.
>>5 - (Access is denied)
>>The subscription at Subscriber 'PTERADON' cannot be initialized
>>immediately because the snapshot for this publication is not yet
>>available. To initialize the subscription, start the Distribution Agent
>>after the snapshot is available.
>>
> ***************************************************************************
>>SQLServerAgent is running on the Server "Dino", so I don't know why I am
>>getting that message.
>>Also, in the Replication Monitor, almost all the folders have a red
>>circle with an X in it.
>>In the "Snapshot agent" folder I have an item "northwind" (which is what
>>I am trying to publish), with the following message:
>>The process could not bulk copy out of table
>>'[dbo].[syncobj_0x4630333239354338]'.
>>In the "log reader agents", I get the following:
>>The license for this installation of SQL Server does not permit Log
>>Reader Agent to run at the Publisher.
>>Could not get license information correctly.
>>I also get the License message for the distribution agents.
>>What License are they talking about?
>>Thanks,
>>Tom.
>>
>

replication please help

Hi gurus, plz help me out!

SNAPSHOT! :mad:
Publisher: 1.5 GB of size. Push merge subscription.256 K full duplex internet connection.
Subscriber: physically at different country. T1 connection. I dial VPN to connect to the publisher which is in seperate domain. Since the domains are different, i am using SQL authentication for my replication process.

The problem with the snapshot is "disconnectivity". Merge agent starts form beginning after running for 2 or 3 hours. I have following entries for MSrepl_errors table in the distribution database:
error_code -2147201001 "The process could not deliver the snapshot to the Subscriber"
error_code 20037 "The process could not bulk copy into table '"dbo"."MY_TABLE"'"
error_code 11 "General network error. Check your network documentation."

The thing that bothers me much is that the VPN scarcely disconnects, only a single packet drop forces the merge agent to retry!!!. To isolate the problem i started ping reqest from publisher to subscriber; i saw merge agent to fail when a packet loss occured for only one second. VPN did not disconnect.
Currently i've chosen "slow link" profile for merge agent.

I started the snapshot 2 days ago and it restarts after every 2 or 3 hours.

Why the heck merge agent starts from the beginning; couldn't it be handled to start where it was when the connection was lost? Packet-loss is normal on the internet connections. I would love to know how u people replicate VLDBs over the internet.
I tried dynamic snapshot but found it rather risky; the merge agent stops with success during the middle of snapshot if connection is dropped leaving the subscriber with inconsistent data.
Any ideas and tips would be very much appreciated.

Howdy!I need u Guys!! :(|||An awful lot depends on what got lost, and where it got lost in the process. Merge replication is also a hodge-podge kind of thing, it is usually "interesting" trying to figure out where the "beginning" of it is, since it scarcely differentiates the difference between tables, much less any order to their changes.

Connections are definitely not "parts is parts" around the world. A connection from one part of the US to another is frequently "rock solid". A connection from here to London is very nearly as good, as is one from London to Sydney. One from the United States to Sydney is absolutely awful. So, we move the data going to Sydney through London... Even though it ends up going most of the way around the world instead of only about one fourth of the way, it is still ots more reliable.

Unless you have lots of time, energy, and money, this is where I'd bring in the "hired guns" to solve the problem. If you bring in someone like Microsoft Professional Services that deals with the various IP providers, knows the problems that exist between point A and point B, and understands the way that your specific replication setup is configured, you'll get an answer much faster and in the long run cheaper than trying to find the solution yourself.

-PatP|||Hi, Pat. Thanx for ur feedback.
I've tried this thing.
Publisher name SERVER1
Subscriber name SERVER2
I uploaded the SNAPSHOT.CAB (300 MB) from the publisher using download manager (if connection disconnects, it resumes where the connection was lost). It got uploaded in 3 hours.
Now i dropped the push merge subscription. Created Pull merge subscription at SERVER2. Placed the SNAPSHOT.CAB into local C drive of SERVER2.
The location i've extracted the snapshot file is:
C:\unc\SERVER1_MBDB_MBDB_PUBLICATION\2004061923325 2
In the Snapshot Location dialogbox for pull merge agent, I specified this location to force the agent to pick snapshot locally.
When i run the merge agent; it fails, for it searches the snapshot files from the default location at the publisher rather than the one i specified :mad: . The error is:

The schema script '\\SERVER1\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\unc\SERVER1_MBDB_MBDB_PUBLIC ATION\20040619233252\UR_TABLE_1.sch' could not be propagated to the subscriber.

Could not find the cabinet file 'snapshot.cab' in folder 'c:\unc\SERVER1_MBDB_MBDB_PUBLICATION\200406192332 52\unc\SERVER1_MBDB_MBDB_PUBLICATION\2004061923325 2\'

How can i square this location problem.
Any Help!!

Thanx for bearing along!|||If you are using a Merge PULL subscription, check the subscription properties at the subscriber to be sure that they specify the correct directory.

I'm a bit nervous about making suggestions, since you are making some pretty significant changes to what you are doing (push versus pull, where the agent exectutes, etc). Be careful to think out what you are doing!

-PatP|||Hi, thanx again 4 ur reply.
I did specify the correct directory where i placed the snapshot files. But the merge agent tries to access the snapshot from publisher's default directory rather than the local path.

I am tryin to use pull instead of push, for push won't work in my case due to disconnection. However i could move the whole snapshot.cab file to subscriber using a download manager despite the connection is lost b/w the transfer. But it isn't working either here. :confused:

Replication object changes

Does replication allow object changes? I read that in SQL server 2000 it will
update new columns on the Publisher and push them to the subscriber, but does
that mean if create a new stored proc on the publisher it will push that as
well to the subscriber? Thanks!
Anita,
for a new stored proc, you could add it to an existing publication, snapshot
and distribute, or create a new publication. A new Stored Proc won't be
picked up automatically. Also, sp_addscriptexec can be used to propagate to
all subscribersif you just want to get it there. Remember that changes to
the stored proc tsql are not picked up and propagated - we need sql 2005 for
this.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks Paul!
"Paul Ibison" wrote:

> Anita,
> for a new stored proc, you could add it to an existing publication, snapshot
> and distribute, or create a new publication. A new Stored Proc won't be
> picked up automatically. Also, sp_addscriptexec can be used to propagate to
> all subscribersif you just want to get it there. Remember that changes to
> the stored proc tsql are not picked up and propagated - we need sql 2005 for
> this.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>

replication not happening

Since deleting a lot of data from our server, we are having a problem
with one of the (push) merge-replicated servers.
Data was deleted from one table ("Scan" table)
Table has ~ 60 million rows, we deleted in batches, a total of about
3 million rows.
SQL1 is merge replicated with SQL2 (on our LAN in Sydney) and with
SQL3 ( 1Mb link to Melbourne)
Since doing this, (SQL2 is fine) we have had a problem with SQL3.
Symptoms
Agent always shows as running (the small graphic shows the
"play" icon not the "stopped" icon), even after stopping it (although the
context menu correctly shows the relevant start or stop option as expected).
Here are the error details from the Merge agent
<<...OLE_Obj...>>
Attached is the log created by the Merge agent in question.
I did a google on the error, only 1 site hit which suggested the
logging be added to the agen t(which I did, hence the attached verbose log)
otherwise I could find nothing useful.
I have tried changing the Agent profile to use a custom one which
has a query timeout of 1000 (secs) instead of the default 300. No luck.
could you post the results of log output to this newsgroup as opposed to
attaching it. Both the image and the log did not make it.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Ishan Bhalla" <IshanBhalla@.discussions.microsoft.com> wrote in message
news:3546E77E-1F51-4510-B948-55066A23F7AF@.microsoft.com...
> Since deleting a lot of data from our server, we are having a
problem
> with one of the (push) merge-replicated servers.
> Data was deleted from one table ("Scan" table)
> Table has ~ 60 million rows, we deleted in batches, a total of
about
> 3 million rows.
>
> SQL1 is merge replicated with SQL2 (on our LAN in Sydney) and
with
> SQL3 ( 1Mb link to Melbourne)
> Since doing this, (SQL2 is fine) we have had a problem with SQL3.
>
> Symptoms
> Agent always shows as running (the small graphic shows the
> "play" icon not the "stopped" icon), even after stopping it (although the
> context menu correctly shows the relevant start or stop option as
expected).
> Here are the error details from the Merge agent
> <<...OLE_Obj...>>
>
> Attached is the log created by the Merge agent in question.
> I did a google on the error, only 1 site hit which suggested the
> logging be added to the agen t(which I did, hence the attached verbose
log)
> otherwise I could find nothing useful.
>
> I have tried changing the Agent profile to use a custom one which
> has a query timeout of 1000 (secs) instead of the default 300. No luck.
>

Replication is failing due to use of FTS on my subscriber, what can I do?

Hi Daniel,
If you are using push subscriptions from a SQL2000 distributor, you are
essentially using the SQL2000 replication components which, I am sorry to
say, are ill-equipped to handle things like full-text indexes during
snapshot processing. This also means that upgrading the subscriber to
SQL2005 SP2 will probably not do you any good. Alternatively, you can use a
SQL2005 SP2 instance as the distributor of your SQL2000 publisher so you can
enable the FulltextIndex (0x0000000001000000) article schema option via
sp_add|changearticle (both SQL2000 and SQL2005 GUI will not allow you to
specify that for a SQL2000 publisher) and let the SQL2005 replication
components handle the full-text index dependencies for you (ideally using
"drop" as the article pre-creation commands). That said, I can imagine that
moving the distributor can involve a substantial amount of work.
Hope that helps,
-Raymond
"Daniel Crichton" <msnews@.worldofspack.com> wrote in message
news:uAOtEPAjHHA.1272@.TK2MSFTNGP04.phx.gbl...
> I'm in the middle of setting up a non-updating transactional replication
> from SQL Server 2000 SP3 (can't put SP4 on as the main application we use
> hasn't been certified for SP4 yet) to SQL Server 2005 SP1 (I could put SP2
> on if it will fix the issue, but it would mean taking our e-commerce sites
> down while doing so and I'd need to schedule a maintenance window for
> this). At first it was working fine, but snapshots were set to delete the
> tables and so we'd lose the FTS setups. I've now changed the snapshots to
> not do this, and now the replications fails with the error:
> Cannot drop index 'PK_Product' because it enforces the full-text key for
> table or indexed view 'Product'.
> This occurs with both "Delete data. If article has a row filter, delete
> only data that matches the filter.", "Truncate all data in the existing
> object" (which is the preferred option), and "Keep existing object
> unchanged". It also doesn't matter if I have the clustered and/or
> nonclustered index copy set to true or false (the PK is the clustered
> index on this table).
> This is a push subscription, with the distribution agent running on the
> publisher.
> Any ideas how I can retain the table structure (so keeping the FTS index
> and not having to rebuild it each time the snapshot is applied) and have
> transaction replication working? Or is it not possible?
> Dan
>
Hi Daniel,
I probably don't understand all the details about your scenario but given
that applying a snapshot typically replaces most of the data at the
subscriber, I would think that a FTS rebuild is likely required (or at least
a good idea) after the snapshot has been applied. That said, we no longer
drop the primary key\unique constraints (which is an arguably bad fix for
some other issue) in a "mostly" SQL2005 environment (SQL2005 snapshot and
distribution agent) if the article pre-creation is 'delete'. However,
leaving any unique constraints\indexes (especially non-clustered) while the
snapshot is being applied runs the risk of slowing down the snapshot
delivery process significantly (no minimal logging) and may prevent a
concurrent snapshot from being delivered successfully since bcp data
generated for a concurrent snapshot can violate uniqueness constraints
(compensated later on during the reconciliation phase).
-Raymond
"Daniel Crichton" <msnews@.worldofspack.com> wrote in message
news:eLx1McKjHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Raymond wrote on Tue, 1 May 2007 09:54:35 -0700:
>
> It seems strange that all options require the PK to be dropped - I would
> have thought that the options to delete or truncate data in the
> destination table would leave the PK untouched (after all, it shouldn't be
> touching the schema). I don't have an FTS index on the SQL Server 2000
> source tables - the FTS is handled solely on the subscriber, so I'm not
> trying to replicate the FTS catalog, just the data in the tables so that
> the change tracking on the subscriber handles all the FTS work.
> Dan
>
|||Hi Daniel,
I probably don't understand all the details about your scenario but given
that applying a snapshot typically replaces most of the data at the
subscriber, I would think that a FTS rebuild is likely required (or at least
a good idea) after the snapshot has been applied. That said, we no longer
drop the primary key\unique constraints (which is an arguably bad fix for
some other issue) in a "mostly" SQL2005 environment (SQL2005 snapshot and
distribution agent) if the article pre-creation is 'delete'. However,
leaving any unique constraints\indexes (especially non-clustered) while the
snapshot is being applied runs the risk of slowing down the snapshot
delivery process significantly (no minimal logging) and may prevent a
concurrent snapshot from being delivered successfully since bcp data
generated for a concurrent snapshot can violate uniqueness constraints
(compensated later on during the reconciliation phase).
-Raymond
"Daniel Crichton" <msnews@.worldofspack.com> wrote in message
news:eLx1McKjHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Raymond wrote on Tue, 1 May 2007 09:54:35 -0700:
>
> It seems strange that all options require the PK to be dropped - I would
> have thought that the options to delete or truncate data in the
> destination table would leave the PK untouched (after all, it shouldn't be
> touching the schema). I don't have an FTS index on the SQL Server 2000
> source tables - the FTS is handled solely on the subscriber, so I'm not
> trying to replicate the FTS catalog, just the data in the tables so that
> the change tracking on the subscriber handles all the FTS work.
> Dan
>

Replication in SQL

Hi,
I have 2 server A & B which A has been set up to push the data over to B
However, i found that B's structure is not correct so i intend to backup A
and retorse into B , will the replication to B fail after restoration from
the backup of A ?
tks & rdgs
Once you make a copy of A -> B then both A and B are in sync.
In this case, as per my knowledge, the replication should not fail
best Regards,
Chandra
http://chanduas.blogspot.com/
"maxzsim" wrote:

> Hi,
> I have 2 server A & B which A has been set up to push the data over to B
> However, i found that B's structure is not correct so i intend to backup A
> and retorse into B , will the replication to B fail after restoration from
> the backup of A ?
> tks & rdgs

Replication in SQL

Hi,
I have 2 server A & B which A has been set up to push the data over to B
However, i found that B's structure is not correct so i intend to backup A
and retorse into B , will the replication to B fail after restoration from
the backup of A ?
tks & rdgsOnce you make a copy of A -> B then both A and B are in sync.
In this case, as per my knowledge, the replication should not fail
best Regards,
Chandra
http://chanduas.blogspot.com/
---
"maxzsim" wrote:

> Hi,
> I have 2 server A & B which A has been set up to push the data over to B
> However, i found that B's structure is not correct so i intend to backup A
> and retorse into B , will the replication to B fail after restoration from
> the backup of A ?
> tks & rdgs

Replication in SQL

Hi,
I have 2 server A & B which A has been set up to push the data over to B
However, i found that B's structure is not correct so i intend to backup A
and retorse into B , will the replication to B fail after restoration from
the backup of A ?
tks & rdgsOnce you make a copy of A -> B then both A and B are in sync.
In this case, as per my knowledge, the replication should not fail
--
best Regards,
Chandra
http://chanduas.blogspot.com/
---
"maxzsim" wrote:
> Hi,
> I have 2 server A & B which A has been set up to push the data over to B
> However, i found that B's structure is not correct so i intend to backup A
> and retorse into B , will the replication to B fail after restoration from
> the backup of A ?
> tks & rdgs

Replication in 2005

We need to push all the changes across network to a secondary, reporting
server, on a timely manner. We were using replication in SQL200, but it
takes a lot server resources. Any new feathers in SQL2005?
There are a lot of new features in SQL 2005. Transactional replication will
place fewer locks on the publisher by default during snapshot generation.
You could also look at database snapshots or log shipping for this.
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
"awan" <awan@.discussions.microsoft.com> wrote in message
news:5D8A9D21-2AF4-4EB7-AAFA-603FCDA399FA@.microsoft.com...
> We need to push all the changes across network to a secondary, reporting
> server, on a timely manner. We were using replication in SQL200, but it
> takes a lot server resources. Any new feathers in SQL2005?