Basic question about replication

Hi,
I am a newbie to replication. I recently joined a company where I have a SQL
Server running 2000 SP3 and I see a distribution database and Replication
Monitor in the Enterprise Manager.
On going to Tools->Replication ->Configure Publishing, Subscribers and
Distribution a pop-up window comes up. In this window under the Publishers
tab, the name of the Server comes up as selected. In the subscribers tab an
ODBC data source is selected. However, in the Publications database tab, NO
database name is checked.
I want to delete the distribution database. Can I safely assume that no
replication is taking place, since no database has been selected for
replication? Or is there a way to find out if any replication is taking
place? Thanks in advance.Hi,
I am not sure but you can check this by executing
sp_helpreplicationoption
Shows the types of replication options enabled for a server. This stored
procedure is executed at the Publisher on the publication database. Take help
of books onile also.
Manu
"sharman" wrote:
> Hi,
> I am a newbie to replication. I recently joined a company where I have a SQL
> Server running 2000 SP3 and I see a distribution database and Replication
> Monitor in the Enterprise Manager.
> On going to Tools->Replication ->Configure Publishing, Subscribers and
> Distribution a pop-up window comes up. In this window under the Publishers
> tab, the name of the Server comes up as selected. In the subscribers tab an
> ODBC data source is selected. However, in the Publications database tab, NO
> database name is checked.
> I want to delete the distribution database. Can I safely assume that no
> replication is taking place, since no database has been selected for
> replication? Or is there a way to find out if any replication is taking
> place? Thanks in advance.
>

Basic problems with replication

Hi
I've just installed Sql Server 7 and wanted to see how replication works.
With DTS i copied Northwind database so now i have two db Northwind and
Northwind_copy on my server.
Using wizards (default values) I've tried snapshot replication from
Northwind (publication) to Northwind_copy (pull subscription, I used sa
login without password ? is it correct ? ).
It seems easy but doesn't work ;(
Snapshot agent session details:
7) The process could not bulk copy out of table
'[dbo].[syncobj_0x3044324641344544]'
6) Bulk copied snapshot data for article 'Categories' (0 rows)
5) Bulk copying snapshot data for article 'Categories'
4) Locking published tables while generating the snapshot
3) Generating Schema script for article 'Categories'
2) Connecting to Publisher 'MyServer'
1) Initializing
In Pull Substraction window:
Could not get license information correctly. The step failed
Thanks
urga
Hi,
For Snapshot replication , no need to copy the objects to Northwind_copy
database. Automatically snapshot replication will copy the selected
articles to destination database.
Licensing:-
- check the licensing in control panel and see how many license you have for
sql 7
- check this registry key as well for previlages..
hklm\system\currentcontrolset\services\licenseinfo \mssql7.0
-- Apply SP4 for SQL 7 snd check.
Thanks
Hari
MCDBA
"urga" <urga@.go2.pl> wrote in message
news:cbtu2h$r0f$1@.nemesis.news.tpi.pl...
> Hi
> I've just installed Sql Server 7 and wanted to see how replication works.
> With DTS i copied Northwind database so now i have two db Northwind and
> Northwind_copy on my server.
> Using wizards (default values) I've tried snapshot replication from
> Northwind (publication) to Northwind_copy (pull subscription, I used sa
> login without password ? is it correct ? ).
> It seems easy but doesn't work ;(
> Snapshot agent session details:
> 7) The process could not bulk copy out of table
> '[dbo].[syncobj_0x3044324641344544]'
> 6) Bulk copied snapshot data for article 'Categories' (0 rows)
> 5) Bulk copying snapshot data for article 'Categories'
> 4) Locking published tables while generating the snapshot
> 3) Generating Schema script for article 'Categories'
> 2) Connecting to Publisher 'MyServer'
> 1) Initializing
> In Pull Substraction window:
> Could not get license information correctly. The step failed
> Thanks
> urga
>
>
sql

Balancing the Data ,Replication ?

Hi,

I have two sets of data i.e two instances of SQL server in two different cities. Data entry happens at both the places.I need to balance the data in two servers i.e. I need to Synchronize the data.

Currently I am Exchanging the data between two sides and using a Buffer database to update the incremental infromation.(Running a SQL script).

I have GUID columns in my database. I am too new to replication.I wanted to know whether I can implement repliaction and what changes i need to make?(e.g. Replacing GUID columns with Identity columns).
Permanent connectivity between two databases is required or Replication can be performed whenever connected?

Best Regards
RohitCan two databases having GUID columns can be replicated or needs to be altered to Integer column

Bad replication performance in SQL2k5 on links with high latency

I tested replication performance on slow network channels, for SQL2k and
SQL2k5. And quite disapplointed by SQL2k5 results...
Network channels were simulated, ping time 200 ms between distributor and
subscriber, unlimited bandwidth.
I tested how many transactions replication can deliver to subsciber. All
transactions are nearby same, they represent typical transactions in my
system.
Publisher, distributor and subsciber are all located on different computers.
In order to check capabilities of hardware, on each of the computers I run
tests to check speed of how many transactions per second it may insert into
database with turned on replication. For each computer, result was ~112
transactions per second, both for SQL2k and SQL2k5.
Next I started to measure replication delivery rate, how many transactions
per second distributor will be able to deliver to subscriber.
In SQL2k, replication in such condition was able to deliver 9 transactions
per second. The best result was obtained with 1 sec polling interval for log
reader and distribution agent, 64kb packet size for distribution agent. No
more differences from default profile.
In case if turn off network delay, rate of inserting transactions on
publisher become same as rate of delivering - replication start to deliver
~112 transactions per second.
For SQL2k5, results were around 5 transactions per second. The best result
was obtained on 1 sec polling interval for log reader and distribution agent,
64kb packet size for distribution agent, 3 SubscriptionStreams. No more
differences from default profile. If turn off network delays, it again
deliver at same rate as it inserting on publisher, about 112 transactions per
second.
Network delay simulator was tested several times to check is it really
simulate network delays as expected. All tests showed correct work of network
delay simulator. For simulating network delays, was used Shundra Cloud.
The question is - Is the replication in SQL2k5 really lost performance in
comparison with SQL2k? Is anything can be done to improve replication
delivery rate in SQL2k5?
the distribution agents in SQL 2005 has autosense network link technology
built into them. They will close down when they detect the link going down
and start up again when it is reconnected. I suspect you are bumping into
this.
I would open a support incident with MS to see if you can disable this
behavior or troubleshoot it further.
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
"andsm" <andsm@.discussions.microsoft.com> wrote in message
news:D153A24B-63DF-45A6-A4B4-22A00221CA29@.microsoft.com...
>I tested replication performance on slow network channels, for SQL2k and
> SQL2k5. And quite disapplointed by SQL2k5 results...
> Network channels were simulated, ping time 200 ms between distributor and
> subscriber, unlimited bandwidth.
> I tested how many transactions replication can deliver to subsciber. All
> transactions are nearby same, they represent typical transactions in my
> system.
> Publisher, distributor and subsciber are all located on different
> computers.
> In order to check capabilities of hardware, on each of the computers I run
> tests to check speed of how many transactions per second it may insert
> into
> database with turned on replication. For each computer, result was ~112
> transactions per second, both for SQL2k and SQL2k5.
> Next I started to measure replication delivery rate, how many transactions
> per second distributor will be able to deliver to subscriber.
> In SQL2k, replication in such condition was able to deliver 9 transactions
> per second. The best result was obtained with 1 sec polling interval for
> log
> reader and distribution agent, 64kb packet size for distribution agent. No
> more differences from default profile.
> In case if turn off network delay, rate of inserting transactions on
> publisher become same as rate of delivering - replication start to deliver
> ~112 transactions per second.
> For SQL2k5, results were around 5 transactions per second. The best result
> was obtained on 1 sec polling interval for log reader and distribution
> agent,
> 64kb packet size for distribution agent, 3 SubscriptionStreams. No more
> differences from default profile. If turn off network delays, it again
> deliver at same rate as it inserting on publisher, about 112 transactions
> per
> second.
> Network delay simulator was tested several times to check is it really
> simulate network delays as expected. All tests showed correct work of
> network
> delay simulator. For simulating network delays, was used Shundra Cloud.
> The question is - Is the replication in SQL2k5 really lost performance in
> comparison with SQL2k? Is anything can be done to improve replication
> delivery rate in SQL2k5?
|||But network, during the tests, is not goes down - it is always work, at
constant ping time.
"Hilary Cotter" wrote:

> the distribution agents in SQL 2005 has autosense network link technology
> built into them. They will close down when they detect the link going down
> and start up again when it is reconnected. I suspect you are bumping into
> this.
> I would open a support incident with MS to see if you can disable this
> behavior or troubleshoot it further.
> --
> 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
>
> "andsm" <andsm@.discussions.microsoft.com> wrote in message
> news:D153A24B-63DF-45A6-A4B4-22A00221CA29@.microsoft.com...
>
>
|||I would open a support incident with Microsoft on this one.
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
"andsm" <andsm@.discussions.microsoft.com> wrote in message
news:D9A495E2-6AD2-480E-B78F-A999A3781FC6@.microsoft.com...[vbcol=seagreen]
> But network, during the tests, is not goes down - it is always work, at
> constant ping time.
> "Hilary Cotter" wrote:

Bad code clogs replication

I am using Transaction replication on sql2005 SP2.
When deploying a new stored procedure that is supposed to be tested, I
got an error stateing that the number of columns in the select did not
match the number in the insert. I checked the SP and it was fine.
1) Was this really relating to the code, or was there an error in
replication?
2) How do you clear 'bad' transactions from replication?
Thanks,
Peter Cwik
Use the skiperror parameter on the distribution agent to skip these
errors for transactional replication.
Can you provide me with the code for the proc in question. I have not
encountered such an error yet in SQL Server.
I normally deploy changes to procs using sp_addscriptexec.
On Jan 8, 2:15 pm, PeterCwik <pjc...@.gmail.com> wrote:
> I am using Transaction replication on sql2005 SP2.
> When deploying a new stored procedure that is supposed to be tested, I
> got an error stateing that the number of columns in the select did not
> match the number in the insert. I checked the SP and it was fine.
> 1) Was this really relating to the code, or was there an error in
> replication?
> 2) How do you clear 'bad' transactions from replication?
> Thanks,
> Peter Cwik

Backupstrategy for Database with Merge-Push Replication.

I have a database on a MSSQL 2000 Server which is replicated by a merge push
replication to approximately 20 Notebooks running MSDE.
backup on the Server is done once per night.
If I decide to go back one night on the server, changes which have been
replicated on the notebooks since then will be reapllied.
Is there a strategy better then stopping publication to all notebooks ,
restoring the backup on the server and repushing the publication to the
clients afterwards?Norbert,
Your plan sounds good to me, can't think of a better way.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Kraft, Norbert wrote:
> I have a database on a MSSQL 2000 Server which is replicated by a merge pu
sh
> replication to approximately 20 Notebooks running MSDE.
> backup on the Server is done once per night.
> If I decide to go back one night on the server, changes which have been
> replicated on the notebooks since then will be reapllied.
> Is there a strategy better then stopping publication to all notebooks ,
> restoring the backup on the server and repushing the publication to the
> clients afterwards?
>
>|||Sounds to be a very cumbersom procedure if done by hand. Anyone who had
prepared a sql-DMO script for a similar case ?
"Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
news:%23wQQT%23T$EHA.3588@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Norbert,
> Your plan sounds good to me, can't think of a better way.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Kraft, Norbert wrote:
push[vbcol=seagreen]

Backupstrategy for Database with Merge-Push Replication.

I have a database on a MSSQL 2000 Server which is replicated by a merge push
replication to approximately 20 Notebooks running MSDE.
backup on the Server is done once per night.
If I decide to go back one night on the server, changes which have been
replicated on the notebooks since then will be reapllied.
Is there a strategy better then stopping publication to all notebooks ,
restoring the backup on the server and repushing the publication to the
clients afterwards?Norbert,
Your plan sounds good to me, can't think of a better way.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Kraft, Norbert wrote:
> I have a database on a MSSQL 2000 Server which is replicated by a merge push
> replication to approximately 20 Notebooks running MSDE.
> backup on the Server is done once per night.
> If I decide to go back one night on the server, changes which have been
> replicated on the notebooks since then will be reapllied.
> Is there a strategy better then stopping publication to all notebooks ,
> restoring the backup on the server and repushing the publication to the
> clients afterwards?
>
>|||Sounds to be a very cumbersom procedure if done by hand. Anyone who had
prepared a sql-DMO script for a similar case ?
"Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
news:%23wQQT%23T$EHA.3588@.TK2MSFTNGP10.phx.gbl...
> Norbert,
> Your plan sounds good to me, can't think of a better way.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Kraft, Norbert wrote:
> > I have a database on a MSSQL 2000 Server which is replicated by a merge
push
> > replication to approximately 20 Notebooks running MSDE.
> > backup on the Server is done once per night.
> > If I decide to go back one night on the server, changes which have been
> > replicated on the notebooks since then will be reapllied.
> > Is there a strategy better then stopping publication to all notebooks ,
> > restoring the backup on the server and repushing the publication to the
> > clients afterwards?
> >
> >
> >

Backupstrategy for Database with Merge-Push Replication.

I have a database on a MSSQL 2000 Server which is replicated by a merge push
replication to approximately 20 Notebooks running MSDE.
backup on the Server is done once per night.
If I decide to go back one night on the server, changes which have been
replicated on the notebooks since then will be reapllied.
Is there a strategy better then stopping publication to all notebooks ,
restoring the backup on the server and repushing the publication to the
clients afterwards?
Norbert,
Your plan sounds good to me, can't think of a better way.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Kraft, Norbert wrote:
> I have a database on a MSSQL 2000 Server which is replicated by a merge push
> replication to approximately 20 Notebooks running MSDE.
> backup on the Server is done once per night.
> If I decide to go back one night on the server, changes which have been
> replicated on the notebooks since then will be reapllied.
> Is there a strategy better then stopping publication to all notebooks ,
> restoring the backup on the server and repushing the publication to the
> clients afterwards?
>
>
|||Sounds to be a very cumbersom procedure if done by hand. Anyone who had
prepared a sql-DMO script for a similar case ?
"Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
news:%23wQQT%23T$EHA.3588@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Norbert,
> Your plan sounds good to me, can't think of a better way.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Kraft, Norbert wrote:
push[vbcol=seagreen]

Backups with differntial & Transactional

Hi friends, Good Morning

Hey there is a question, i have two servers where replication is implemented, The two servers is used to take backup on dailybasis, on one server we take differential backup, and on second server we take transactional backup on same time, when we restore the backups on the opposite servers (backup taken on 1st server will be restored on 2nd server and 2nd server backup will be restored on 1st server)what are contents u find difference in the dataIs that how you implemented replication? By crossing the restores?|||Take a look - it will help you to know more details about backuping for replicated databases

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/replsql/replbackup_8enn.asp

backups getting huge

Is replication suppose to continually grow the database backups on the
distribution machine? I had to remove replication because the backups grew a
couple gig in about a months time. Am I missing something? I've tried this
twice now with the same results. Thanks.
for merge it may. For transactional it shouldn't if your log reader agent is
running frequently.
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
"s" <s@.discussions.microsoft.com> wrote in message
news:9B0AD4A6-D102-486C-9FAF-9091B954E9A3@.microsoft.com...
> Is replication suppose to continually grow the database backups on the
> distribution machine? I had to remove replication because the backups grew
a
> couple gig in about a months time. Am I missing something? I've tried this
> twice now with the same results. Thanks.
|||Thanks for the reply. I was using snapshot replication. Would this also
create continually growing backups? Is there any way to get around this
effect?
"Hilary Cotter" wrote:

> for merge it may. For transactional it shouldn't if your log reader agent is
> running frequently.
> --
> 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
> "s" <s@.discussions.microsoft.com> wrote in message
> news:9B0AD4A6-D102-486C-9FAF-9091B954E9A3@.microsoft.com...
> a
>
>

Backups

Hi All,
We have setup Transactional Replication with queued updating subscribers option. Our Servers are in Failover cluster with windows 2000 AS. We are doing Full and Transactional log backups as usual. Can any one suggest what are the recovery scenarios, in ca
se of Publisher (if it is completely down, I mean all clusters are down) and User interactions to Subscriber immediately, so that data is more than of Publisher db.
Please provide us valuable suggestions.
Thanks,
John.
I'm not exactly sure what your question is. You loose me with this statement
:
"so that data is more than of Publisher db. "
With queued Updating, your Subscriber is essentially a mirror of your
Publisher's data. If your Publisher goes offline permanently you will lose
transactions that are on your publisher and haven't made their way back to
the Subscriber.
So, its not too hard to clone your Subscriber to rebuild your Publisher. To
do this you would have to drop your subscriber, copy the subscriber schema
and data to the publisher, re run your publication scripts on your new
publisher, and do a no-sync subscription.
If your Publisher goes offline for an extended period your chance of
bringing it back on line without conflicts increases. With Queued Updating
the conflict view only lets you view conflicts, not resolve them.
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:1D2A989A-5347-4E74-AAD6-707E9EC9CE70@.microsoft.com...
> Hi All,
> We have setup Transactional Replication with queued updating subscribers
option. Our Servers are in Failover cluster with windows 2000 AS. We are
doing Full and Transactional log backups as usual. Can any one suggest what
are the recovery scenarios, in case of Publisher (if it is completely down,
I mean all clusters are down) and User interactions to Subscriber
immediately, so that data is more than of Publisher db.
> Please provide us valuable suggestions.
> Thanks,
> John.
>
|||The best suggestion I have is to look in BOL for the article about the
"synch with backup" option that can be used. This will not only walk you
through these scenarios, but explain how to create coherent, multi-server
backups.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com

Backups

I have transactional replication topology where each component is on
its own server. I currently backup the t-logs every 15 minutes with a
differential at noon and a full back up at midnight.
Is it necessary for me to create the exact same backup strategy at the
distributor and subscriber? Or would a full backup with less frequent
t-log backups be sufficient for the distribution and subscription
databases?As you did not mention which version of your SQL Server, I'll post 2
choices.
There is an article about "Strategies for Backing Up and Restoring
Transactional Replication" for SQL Server 2000 in Books Online. You may want
to check it out?
http://msdn2.microsoft.com/en-us/library/aa237094(SQL.80).aspx
And this is for SQL Server 2005:
http://msdn2.microsoft.com/en-us/library/ms152560.aspx
--
Ekrem Önsoy
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191534232.786974.23060@.o80g2000hse.googlegroups.com...
>I have transactional replication topology where each component is on
> its own server. I currently backup the t-logs every 15 minutes with a
> differential at noon and a full back up at midnight.
> Is it necessary for me to create the exact same backup strategy at the
> distributor and subscriber? Or would a full backup with less frequent
> t-log backups be sufficient for the distribution and subscription
> databases?
>

Backup/Restore: Restoring to new server without rerunning a snapshot

I am designing a solution that utilizes replication from a front-end database to a back-end database. Historical data will be truncated from the front-end database in such a way that these truncation deletes will not be replicated - thus, the back-end database acts as a historical archive for the front-end database.

I am concerned about backup and restore scenarios for this environment.

Once we have begun truncating data from the front-end database, we will never be able to re-snapshot the database to rebuild the back-end database.

My concern comes if the servers are destroyed and the environment must be rebuilt. For SQL Server 2000, Books Online says:

"When you restore a backup of a replicated database to a server or database other than the one on which it was created, your replication settings cannot be preserved. For publishing databases and merge subscribing databases, a full restore of the database and logs is followed by an automatic removal of replication meta data from the database when the database or server you restore to differs from the one on which the backup was created."

Books Online for SQL Server 2005 has a similar statement. Does this mean that I would be unable to restore my front-end and back-end databases, and reestablish replication without taking a new snapshot? Does SQL 2005 provide any advantages for disaster recovery given this scenario? Does restoring with the KEEP_REPLICATION option override the behavior specified in the above BOL quote?

That isn't correct. You can restore a backup without preserving replication settings and then reconfigure replication in that environment. You would not want to issue a snapshot, so you would simply tell the replication engine that the subscriber already has the schema and data.

Now, there are two different behavior paths. With SQL Server 2000, you would tell it that the subscriber already has the schema and data "nosynch" and a subscription would be created, but changes would fail, because you would have to manually create the replication stored procedures that are called on the subscriber. But, once created, all of the data would flow normally.

With SQL Server 2005, you create the subscription with replication support only. This would not cause a snapshot to be sent to the subscriber, but it would create all of the necessary replication objects.

|||

Hello,

I have read your comments about restoring backup in a diferent server. This is my case and I am really desesperated becuase I am totally unable to do it . I only have a backup from the old server and I have no idea about scripts procedures or programming I am only trying from the SQL SERVER Enterprise Manager. Please let me know if it does really exist the posibility.

Thanks a lot

Carlos

|||did you found any solution for this?

Backup/Restore: Restoring to new server without rerunning a snapshot

I am designing a solution that utilizes replication from a front-end database to a back-end database. Historical data will be truncated from the front-end database in such a way that these truncation deletes will not be replicated - thus, the back-end database acts as a historical archive for the front-end database.

I am concerned about backup and restore scenarios for this environment.

Once we have begun truncating data from the front-end database, we will never be able to re-snapshot the database to rebuild the back-end database.

My concern comes if the servers are destroyed and the environment must be rebuilt. For SQL Server 2000, Books Online says:

"When you restore a backup of a replicated database to a server or database other than the one on which it was created, your replication settings cannot be preserved. For publishing databases and merge subscribing databases, a full restore of the database and logs is followed by an automatic removal of replication meta data from the database when the database or server you restore to differs from the one on which the backup was created."

Books Online for SQL Server 2005 has a similar statement. Does this mean that I would be unable to restore my front-end and back-end databases, and reestablish replication without taking a new snapshot? Does SQL 2005 provide any advantages for disaster recovery given this scenario? Does restoring with the KEEP_REPLICATION option override the behavior specified in the above BOL quote?

That isn't correct. You can restore a backup without preserving replication settings and then reconfigure replication in that environment. You would not want to issue a snapshot, so you would simply tell the replication engine that the subscriber already has the schema and data.

Now, there are two different behavior paths. With SQL Server 2000, you would tell it that the subscriber already has the schema and data "nosynch" and a subscription would be created, but changes would fail, because you would have to manually create the replication stored procedures that are called on the subscriber. But, once created, all of the data would flow normally.

With SQL Server 2005, you create the subscription with replication support only. This would not cause a snapshot to be sent to the subscriber, but it would create all of the necessary replication objects.

|||

Hello,

I have read your comments about restoring backup in a diferent server. This is my case and I am really desesperated becuase I am totally unable to do it . I only have a backup from the old server and I have no idea about scripts procedures or programming I am only trying from the SQL SERVER Enterprise Manager. Please let me know if it does really exist the posibility.

Thanks a lot

Carlos

Backup transaction logs and replication simultaneously

Is there any problem with implementating some kind of replication and
backing up transaction logs at the same time? SQL Server 2000 Standard
Edition

The server is configured to back up log files regularly, with the
presence
of a(New) Disaster recovery server and with an inability for
standby(Standard Edition)I am planning to implement some kind of
replication hopefully still backing up the transaction logs to enable
a point in time recovery.

Thanks in advance for your great ideas

Vincento"Vincento Harris" <wumutek@.yahoo.com> wrote in message
news:2fa13ee7.0409281008.347cee08@.posting.google.c om...
> Is there any problem with implementating some kind of replication and
> backing up transaction logs at the same time? SQL Server 2000 Standard
> Edition
> The server is configured to back up log files regularly, with the
> presence
> of a(New) Disaster recovery server and with an inability for
> standby(Standard Edition)I am planning to implement some kind of
> replication hopefully still backing up the transaction logs to enable
> a point in time recovery.
> Thanks in advance for your great ideas
> Vincento

Check out "Backing Up and Restoring Replication Databases" in Books Online -
it covers each type of replication, as well as how to combine replication
with log shipping.

If that doesn't give you enough information, you could post in
microsoft.public.sqlserver.replication - you might get a more detailed
answer there.

Simon