"Roust_m" <roustam@hotbox.ru> wrote in message
news:a388fd78.0410260029.1039c2d8@posting.google.com...
> Seriously, the safest bet is to script all your replication
> publications/subscriptions to the target server and run the scripts
> after
> you have done the conversion.
>
> - Why would I need to run the scripts for publications/subscriptions
> for servers I do not even touch? Suppose the name of my current
> server is Saturn, I will be using the same name for the default
> instance in the cluster. So I will have those replications as before
> on other servers targeted to Saturn. They will either start or will
> not. If they will not I will have to drop Saturn subscriptions and
> recreate them again. So the question I was asking: Is there a chance
> they will start.
>
> As for publications/subscriptions that go from the server I plan to
> cluster, I will loose them (as I have no idea how to move system
> databases to a cluster)and will have to recreate them manually or with
> scripts (provided I script them in advance) I had bad experience
> using scripts, however. After I restored publications&subscriptions
> with scripts on one of my servers I started to receive an error:
> "Cannot insert the value NULL into column 'publisher', table
> 'tempdb.dbo.MSreplication_agent_status'; column does not allow nulls.
> INSERT fails. " It does not block any replication, but it is
> annoying.
>
> So my question is: will the replications from OTHER servers to my new
> clustered server start, provided I will be using the same name for
> default instance?
>
> "Geoff N. Hiten" <SRDBA@Careerbuilder.com> wrote in message
news:<uRsRL#ruEHA.3024@TK2MSFTNGP15.phx.gbl>...
> > OK Rodney, I agree you are not a SQL guru. :)
> >
> > Seriously, the safest bet is to script all your replication
> > publications/subscriptions to the target server and run the scripts
after
> > you have done the conversion. You could probably hack everything back
> > together after a cluster conversion but I wouldn't want to, especially
when
> > the scripting option works extremely well. I doubt you can use the same
> > name since Cluster SQL Servers are either the default instance for the
> > cluster OR are in the form of VirtualServername\InstanceName and appear
as
> > named instances.
> >
> > --
> > Geoff N. Hiten
> > Microsoft SQL Server MVP
> > Senior Database Administrator
> > Careerbuilder.com
> >
> > I support the Professional Association for SQL Server
> > www.sqlpass.org
> >
> > "Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
> > message news:eFz%239TquEHA.1860@TK2MSFTNGP15.phx.gbl...
> > > I am not a SQL guru (if I am wrong Geoff will hopefully correct me),
but
> > > everything won't just pick right back up. MSDB holds that information
and
> > > will have to rebuilt or setup again.
> > >
> > > Cheers,
> > >
> > > Rod
> > >
> > > MVP - Windows Server - Clustering
> > > http://www.nw-america.com - Clustering
> > > http://msmvps.com/clustering - Blog
> > >
> > > "Roust_m" <roustam@hotbox.ru> wrote in message
> > > news:a388fd78.0410240950.5ff2b59f@posting.google.com...
> > > >I plan to install MS SQL cluster on new hardware, using the same
> > > > nameand IP for one of MS SQL instances, restore user databases (or
> > > > maybe attach them) on the cluster instance and expect the
> > > > transactional replications to from other servers to this cluster
> > > > instance work, as they did for the old server, since I will be using
> > > > the same name and IP address for my virtual instance on the cluster.
> > > >
> > > > "Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote
in
> > > > message news:<uuBiU4CuEHA.3872@TK2MSFTNGP15.phx.gbl>...
> > > >> What is your plan for moving SQL?
> > > >>
> > > >> Rod
> > > >>
> > > >> "Roust_m" <roustam@hotbox.ru> wrote in message
> > > >> news:a388fd78.0410212225.1e922378@posting.google.com...
> > > >> > The name of my present SQL Server is Server1, I will be using the
> > same
> > > >> > name for one of the cluster instances. Will the replications
start
> > > >> > after I cluster the server?
> > > >> >
> > > >> > "Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com>
wrote in
> > > >> > message news:<u6mIGa2tEHA.3088@tk2msftngp13.phx.gbl>...
> > > >> >> You can't use the same name on two instances of SQL at the same
> > time.
> > > >> >> You
> > > >> >> can use a SQL cluster to house transactional
> > > >> >> replications.
> > > >> >>
> > > >> >> Cheers,
> > > >> >>
> > > >> >> Rod
> > > >> >>
> > > >> >> MVP - Windows Server - Clustering
> > > >> >> http://www.nw-america.com - Clustering
> > > >> >> http://www.msmvps.com/clustering - Blog
> > > >> >>
> > > >> >> "Roust_m" <roustam@hotbox.ru> wrote in message
> > > >> >> news:a388fd78.0410210300.c365e24@posting.google.com...
> > > >> >> > Hi!
> > > >> >> >
> > > >> >> > I have a server I am planning to cluster. I will be using the
same
> > > >> >> > SQL
> > > >> >> > server name for this cluster. I have a large number of
> > > >> >> > transactional
> > > >> >> > replications to this server from a dozen of other servers.
Will
> > > >> >> > these
> > > >> >> > replications work evenly after the clustering? (All my
servers
> > are
> > > >> >> > MS
> > > >> >> > SQL2000 sp3 + Win2000 Server sp4)
> > > >> >> >
> > > >> >> >
> > > >> >> >
> > > >> >> > Thanks.
> > >
> > >

"Geoff N. Hiten" <SRDBA@Careerbuilder.com> wrote in message news:<u2f$b62uEHA.3972@TK2MSFTNGP10.phx.gbl>...
> Replicaiton from other servers MIGHT start, but I wouldn't bet my job on it.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
>
> I support the Professional Association for SQL Server
> www.sqlpass.org
>
> "Roust_m" <roustam@hotbox.ru> wrote in message
> news:a388fd78.0410260029.1039c2d8@posting.google.com...
> > Seriously, the safest bet is to script all your replication
> > publications/subscriptions to the target server and run the scripts
> > after
> > you have done the conversion.
> >
> > - Why would I need to run the scripts for publications/subscriptions
> > for servers I do not even touch? Suppose the name of my current
> > server is Saturn, I will be using the same name for the default
> > instance in the cluster. So I will have those replications as before
> > on other servers targeted to Saturn. They will either start or will
> > not. If they will not I will have to drop Saturn subscriptions and
> > recreate them again. So the question I was asking: Is there a chance
> > they will start.
> >
> > As for publications/subscriptions that go from the server I plan to
> > cluster, I will loose them (as I have no idea how to move system
> > databases to a cluster)and will have to recreate them manually or with
> > scripts (provided I script them in advance) I had bad experience
> > using scripts, however. After I restored publications&subscriptions
> > with scripts on one of my servers I started to receive an error:
> > "Cannot insert the value NULL into column 'publisher', table
> > 'tempdb.dbo.MSreplication_agent_status'; column does not allow nulls.
> > INSERT fails. " It does not block any replication, but it is
> > annoying.
> >
> > So my question is: will the replications from OTHER servers to my new
> > clustered server start, provided I will be using the same name for
> > default instance?
> >
> > "Geoff N. Hiten" <SRDBA@Careerbuilder.com> wrote in message
> news:<uRsRL#ruEHA.3024@TK2MSFTNGP15.phx.gbl>...
> > > OK Rodney, I agree you are not a SQL guru. :)
> > >
> > > Seriously, the safest bet is to script all your replication
> > > publications/subscriptions to the target server and run the scripts
> after
> > > you have done the conversion. You could probably hack everything back
> > > together after a cluster conversion but I wouldn't want to, especially
> when
> > > the scripting option works extremely well. I doubt you can use the same
> > > name since Cluster SQL Servers are either the default instance for the
> > > cluster OR are in the form of VirtualServername\InstanceName and appear
> as
> > > named instances.
> > >
> > > --
> > > Geoff N. Hiten
> > > Microsoft SQL Server MVP
> > > Senior Database Administrator
> > > Careerbuilder.com
> > >
> > > I support the Professional Association for SQL Server
> > > www.sqlpass.org
> > >
> > > "Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
> > > message news:eFz%239TquEHA.1860@TK2MSFTNGP15.phx.gbl...
> > > > I am not a SQL guru (if I am wrong Geoff will hopefully correct me),
> but
> > > > everything won't just pick right back up. MSDB holds that information
> and
> > > > will have to rebuilt or setup again.
> > > >
> > > > Cheers,
> > > >
> > > > Rod
> > > >
> > > > MVP - Windows Server - Clustering
> > > > http://www.nw-america.com - Clustering
> > > > http://msmvps.com/clustering - Blog
> > > >
> > > > "Roust_m" <roustam@hotbox.ru> wrote in message
> > > > news:a388fd78.0410240950.5ff2b59f@posting.google.com...
> > > > >I plan to install MS SQL cluster on new hardware, using the same
> > > > > nameand IP for one of MS SQL instances, restore user databases (or
> > > > > maybe attach them) on the cluster instance and expect the
> > > > > transactional replications to from other servers to this cluster
> > > > > instance work, as they did for the old server, since I will be using
> > > > > the same name and IP address for my virtual instance on the cluster.
> > > > >
> > > > > "Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote
> in
> > > > > message news:<uuBiU4CuEHA.3872@TK2MSFTNGP15.phx.gbl>...
> > > > >> What is your plan for moving SQL?
> > > > >>
> > > > >> Rod
> > > > >>
> > > > >> "Roust_m" <roustam@hotbox.ru> wrote in message
> > > > >> news:a388fd78.0410212225.1e922378@posting.google.com...
> > > > >> > The name of my present SQL Server is Server1, I will be using the
> same
> > > > >> > name for one of the cluster instances. Will the replications
> start
> > > > >> > after I cluster the server?
> > > > >> >
> > > > >> > "Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com>
> wrote in
> > > > >> > message news:<u6mIGa2tEHA.3088@tk2msftngp13.phx.gbl>...
> > > > >> >> You can't use the same name on two instances of SQL at the same
> time.
> > > > >> >> You
> > > > >> >> can use a SQL cluster to house transactional
> > > > >> >> replications.
> > > > >> >>
> > > > >> >> Cheers,
> > > > >> >>
> > > > >> >> Rod
> > > > >> >>
> > > > >> >> MVP - Windows Server - Clustering
> > > > >> >> http://www.nw-america.com - Clustering
> > > > >> >> http://www.msmvps.com/clustering - Blog
> > > > >> >>
> > > > >> >> "Roust_m" <roustam@hotbox.ru> wrote in message
> > > > >> >> news:a388fd78.0410210300.c365e24@posting.google.com...
> > > > >> >> > Hi!
> > > > >> >> >
> > > > >> >> > I have a server I am planning to cluster. I will be using the
> same
> > > > >> >> > SQL
> > > > >> >> > server name for this cluster. I have a large number of
> > > > >> >> > transactional
> > > > >> >> > replications to this server from a dozen of other servers.
> Will
> > > > >> >> > these
> > > > >> >> > replications work evenly after the clustering? (All my
> servers
> are
> > > > >> >> > MS
> > > > >> >> > SQL2000 sp3 + Win2000 Server sp4)
> > > > >> >> >
> > > > >> >> >
> > > > >> >> >
> > > > >> >> > Thanks.
> > > >