replication to new server

Hi
I have replication set up and working correctly. However we now have a new
SQL Server and want to set up replication to there(instead of the existing
server). Do we have to go through setting up the whole replication process
again or is there an easier way?
Thanks
I would start from scratch... Server names, etc are stored in the
registry... It is often better to be clean...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"jonjo" <jonjo@.discussions.microsoft.com> wrote in message
news:5BB5248E-F8E2-45A7-8F04-9383C423DD16@.microsoft.com...
> Hi
> I have replication set up and working correctly. However we now have a new
> SQL Server and want to set up replication to there(instead of the existing
> server). Do we have to go through setting up the whole replication process
> again or is there an easier way?
> Thanks
|||Ok Thanks for the advice
"Wayne Snyder" wrote:

> I would start from scratch... Server names, etc are stored in the
> registry... It is often better to be clean...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "jonjo" <jonjo@.discussions.microsoft.com> wrote in message
> news:5BB5248E-F8E2-45A7-8F04-9383C423DD16@.microsoft.com...
>
>
|||Jonjo,
when you say 'set up replication to there' do you mean add a subscription?
If so then adding the subscription is much like any other subscription, and
EM can generate the scripts of an existing subscription to be used as a
template if you like - just change the servername using find and replace and
then run the script on the subscriber. If you mean you want to set up the
second server as a publisher/distributor and have the same publications,
then it depends on the complexity. If it's a few simple publications then
I'd start from scratch. If it's more complex, and you haven't documented
changes to custom profiles, post-snapshot filepaths etc then I'd script out
and edit the script before running it on the new publisher to be sure of
having a replica, and it'll also be much faster.
HTH,
Paul Ibison (SQL Server MVP)

replication to new server

Hi
I have replication set up and working correctly. However we now have a new
SQL Server and want to set up replication to there(instead of the existing
server). Do we have to go through setting up the whole replication process
again or is there an easier way?
ThanksI would start from scratch... Server names, etc are stored in the
registry... It is often better to be clean...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"jonjo" <jonjo@.discussions.microsoft.com> wrote in message
news:5BB5248E-F8E2-45A7-8F04-9383C423DD16@.microsoft.com...
> Hi
> I have replication set up and working correctly. However we now have a new
> SQL Server and want to set up replication to there(instead of the existing
> server). Do we have to go through setting up the whole replication process
> again or is there an easier way?
> Thanks|||Ok Thanks for the advice
"Wayne Snyder" wrote:
> I would start from scratch... Server names, etc are stored in the
> registry... It is often better to be clean...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "jonjo" <jonjo@.discussions.microsoft.com> wrote in message
> news:5BB5248E-F8E2-45A7-8F04-9383C423DD16@.microsoft.com...
> > Hi
> >
> > I have replication set up and working correctly. However we now have a new
> > SQL Server and want to set up replication to there(instead of the existing
> > server). Do we have to go through setting up the whole replication process
> > again or is there an easier way?
> >
> > Thanks
>
>|||Jonjo,
when you say 'set up replication to there' do you mean add a subscription?
If so then adding the subscription is much like any other subscription, and
EM can generate the scripts of an existing subscription to be used as a
template if you like - just change the servername using find and replace and
then run the script on the subscriber. If you mean you want to set up the
second server as a publisher/distributor and have the same publications,
then it depends on the complexity. If it's a few simple publications then
I'd start from scratch. If it's more complex, and you haven't documented
changes to custom profiles, post-snapshot filepaths etc then I'd script out
and edit the script before running it on the new publisher to be sure of
having a replica, and it'll also be much faster.
HTH,
Paul Ibison (SQL Server MVP)sql

Replication row Commit Size

Is there a way to get replication to commit records in batches instead of all at once? I am in a 24/7 shop and some of my updates end up being thousands of rows and it locks the subscriber table for a few minutes sometimes. If I could get it to commit say every 1000 rows it might give me some relief in this area..

Or am I thinking about this wrong? If this is possible, would it help at all...

I

transactional replication adheres to the ACID properties, so if you apply 10,000 commands in one trasaction at the publisher, the distribution agent will apply the same commands in one transaction at the subscriber.

You have a couple options:

1. commit your commands at the publisher in smaller batches. That means if your update statement will affect 100k rows, break it up by updating 1,000 at a time until all 100k are completed.

2. You can use the logreader agent parameter -MaxCmdsInTran, which will break the ACID properties, but allow you to do what you want to do. This has other performance impact, but if you're committing thousands and thousands (or millions) of rows in a single transaction, this can offer some relief. You can find more information about this parameter in Books Online.

I'd recommend #1 before #2.

|||

Thanks for that response... it was what I was expecting to hear but just wanted to check. My servers typically only get updated once a day with major updates and the updates can happen over time as they are not mission critical. The servers are only content related so as long as they get updated they are happy...

Thannks again for the answer.

Replication Problem

When i tries to insert a record at publisher the record is get deleted in the
publisher instead of propagating to subscriber, this is not happening always.
I am using two way merge replication
Thanks
Kailux
It probably happens because of the conflict. Do you see any conflicts
occuring during synch?
MC
"kailux4" <kailux4@.discussions.microsoft.com> wrote in message
news:3D3E1D37-34D4-4C5E-A2AF-1AF2E22FF8A8@.microsoft.com...
> When i tries to insert a record at publisher the record is get deleted in
> the
> publisher instead of propagating to subscriber, this is not happening
> always.
> I am using two way merge replication
> Thanks
> Kailux

Replication Problem

When i tries to insert a record at publisher the record is get deleted in th
e
publisher instead of propagating to subscriber, this is not happening always
.
I am using two way merge replication
Thanks
KailuxIt probably happens because of the conflict. Do you see any conflicts
occuring during synch?
MC
"kailux4" <kailux4@.discussions.microsoft.com> wrote in message
news:3D3E1D37-34D4-4C5E-A2AF-1AF2E22FF8A8@.microsoft.com...
> When i tries to insert a record at publisher the record is get deleted in
> the
> publisher instead of propagating to subscriber, this is not happening
> always.
> I am using two way merge replication
> Thanks
> Kailux

Replication Problem

When i tries to insert a record at publisher the record is get deleted in the
publisher instead of propagating to subscriber, this is not happening always.
I am using two way merge replication
Thanks
KailuxIt probably happens because of the conflict. Do you see any conflicts
occuring during synch?
MC
"kailux4" <kailux4@.discussions.microsoft.com> wrote in message
news:3D3E1D37-34D4-4C5E-A2AF-1AF2E22FF8A8@.microsoft.com...
> When i tries to insert a record at publisher the record is get deleted in
> the
> publisher instead of propagating to subscriber, this is not happening
> always.
> I am using two way merge replication
> Thanks
> Kailux

replication of a view

Is it possible to replicate a view, and have it published to a table instead of a view?I am not sure exactly what you mean.

Do you want the records in the view to be appended to an existing table or do you want to create a new table?

TO append use INSERT INTO

To create a new table from the view:

Inserting Rows Using SELECT INTO
The SELECT INTO statement creates a new table and populates it with the result set of the SELECT. The structure of the new table is defined by the attributes of the expressions in the select list, for example:

SELECT Shippers.*, Link.Address, Link.City,
Link.Region, Link.PostalCode
INTO NewShippers
FROM Shippers
JOIN LinkServer.DB.dbo.Shippers AS Link
ON (Shippers.ShipperID = Link.ShipperID)

SELECT INTO can be used to combine data from several tables or views into one table. It can also be used to create a new table containing data selected from a linked server.

Replication Not working for a table

We have about 20 tables setup for replications . All std.
setup . Replication is using stored procs created by SQL
Server instead of the Statements. All tables are fine
except one table stpped changing data at all. No errors
etc.
What should I do.
Table has 2 coulms as PK . using SQL stored proc,
sp_msIns..,sp_msUpd.., sp_msdel..
What could be wrong. PLease help. All other tables are
fine.
No Primary key or columns have been changed at all .
ThanksYour table name contains white spaces or special characters? If so,
rename your stored procedures.
MoreThanInsane
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1340150.html