Monday, March 19, 2012
New Server and replication
operations' in BOL. Provided the new server and the old
server have the same name, this is possible. You'll need
to take copies of all the publisher/distributor databases
involved - the publishing database, MSDB, distribution
and master. BTW, prevent anyone from accessing the
publishing database and stop all replication jobs inc the
cleanup agent before starting the backup procedures.
HTH,
Paul Ibison SQL Server MVP,
www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Thanks for your reply. The new server has the same name as of old. But
eventually I'll have to change the name of the old server since two machines
with same name cannot belong to the same domain.
How do i set up the subscribers to replicate the data on the old server that
will sit in the branch and then replicate the data on the new server that
has the publisher?
Thanks
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:046901c53435$c318f170$a601280a@.phx.gbl...
> Have a look at 'replication, backup and restore
> operations' in BOL. Provided the new server and the old
> server have the same name, this is possible. You'll need
> to take copies of all the publisher/distributor databases
> involved - the publishing database, MSDB, distribution
> and master. BTW, prevent anyone from accessing the
> publishing database and stop all replication jobs inc the
> cleanup agent before starting the backup procedures.
> HTH,
> Paul Ibison SQL Server MVP,
> www.replicationanswers.com/default.asp
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||I'm not too sure I follow the last bit. As I understand,
you have an existing publisher that will be replaced by a
new publisher server. The new server will have the same
name and the old server taken offline. Form the point of
view of the subscribers, they won't know any difference,
unless they are using IP addresses for registration of
the publisher.
HTH,
Paul Ibison SQL Server MVP,
www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I am sorry If I confused you. You are absolutly correct till now. What I
intend to do now is put our old server in one of our branches. I'll call it
Server1. Server1 is going to be a member of the domain if it makes sense.
Earlier managers used to replicate directly on to the publisher server but
now I want a bunch of managers to replicate to Server1 and rest of them to
Server0 i.e. my new server (Domain Controller). And I want Server1 to
replicate everything onto Server0. Server1 should pickup any relevant
changes from Server0 and pass onto subscribers replicating on Server1.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:108301c53502$00b05510$a501280a@.phx.gbl...
> I'm not too sure I follow the last bit. As I understand,
> you have an existing publisher that will be replaced by a
> new publisher server. The new server will have the same
> name and the old server taken offline. Form the point of
> view of the subscribers, they won't know any difference,
> unless they are using IP addresses for registration of
> the publisher.
> HTH,
> Paul Ibison SQL Server MVP,
> www.replicationanswers.com/default.asp
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Thanks for the clarification. What you are referring to
is 'republishing'. There isn't a huge amount of
information in BOL but there is some. If you are using
merge replication, the same effect could be achieved by
using alternative synchronization partners.
HTH,
Paul Ibison SQL Server MVP,
www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Saturday, February 25, 2012
New features of Broker?
Dear all,
I just got Katmai installed with BOL. But can't find anything useful for SB, i.e. What's New. I understand the doc team must be working on it now. Could anyone tell me:
1. Is Katmai SB still the ver. 1 of SB, or ver. 2?
2. Does Management Studio do more UI support for SB?
3. Will Katmai SB support the B2C scenario, i.e. Laptop behind NATs?
Best regards,
dong
1. Is Katmai SB still the ver. 1 of SB, or ver. 2?
I am not sure exactly what you mean by this question but Katmai is the second version of Sql Server that contains Service Broker. Sql 2005 was the first version that contained support for Service Broker.
2. Does Management Studio do more UI support for SB?
We do have plans to do more for Service Broker in the Management Studio UI in Katmai but that won't be coming until a later CTP.
3. Will Katmai SB support the B2C scenario, i.e. Laptop behind NATs?
Katmai will not have any new features to support Broker behind firewalls. I will send another post on the Service Broker Katmai features
|||Hi Rick!
Nice to meet you here :-)
Here are some features, which might be very useful for the next release of Service Broker:
GUI support in SQL Server Management Studio Service Listing Manager inside SQL Management Studio :-) Multiple Service Broker endpoints per SQL Server Instance Don't deactivate the queue when a poison message occurs, only the serviceNew export option
Has anyone ever heard of or tried adding to the report export list?
I've read through the BOL for report export options and searched the
web for advice. There is quite a bit of information folks have shared
on ways to export stored procedure results to a fixed length text
file. But I haven't found anything on exporting from a report to a
text file.
Is it was possible to export a report into a fixed length text file
from a Reporting Services website report?The only text based export that Reporting Services does is CSV (Comma
Delimited). On adding a type to the export list you would have to write
your own rendering extension to transform the data in the report and that
isn't an easy task. If you look in the rsreportserver.config file you'll
see a <Render> section that contains all of the various rendering
extensions available to Reporting Services.
You can find more information about creating a rendering extension here:
http://msdn2.microsoft.com/en-us/library/ms153624.aspx
One last question. When you say "Fixed length text file" do you mean a
"fixed width" text file or an actual fixed size of the text file being
produced?
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> From: asflp <fpetrivelli@.gmail.com>
> Newsgroups: microsoft.public.sqlserver.reportingsvcs
> Subject: New export option
> Date: Fri, 26 Oct 2007 17:12:18 -0000
> Organization: http://groups.google.com
> Hello Fellow RS
> Has anyone ever heard of or tried adding to the report export list?
> I've read through the BOL for report export options and searched the
> web for advice. There is quite a bit of information folks have shared
> on ways to export stored procedure results to a fixed length text
> file. But I haven't found anything on exporting from a report to a
> text file.
> Is it was possible to export a report into a fixed length text file
> from a Reporting Services website report?
>|||On Oct 26, 10:46 am, cal...@.online.microsoft.com (Chris Alton [MSFT])
wrote:
> The only text based export that Reporting Services does is CSV (Comma
> Delimited). On adding a type to the export list you would have to write
> your own rendering extension to transform the data in the report and that
> isn't an easy task. If you look in the rsreportserver.config file you'll
> see a <Render> section that contains all of the various rendering
> extensions available to Reporting Services.
> You can find more information about creating a rendering extension here:
> http://msdn2.microsoft.com/en-us/library/ms153624.aspx
> One last question. When you say "Fixed length text file" do you mean a
> "fixed width" text file or an actual fixed size of the text file being
> produced?
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
>
> > From: asflp <fpetrive...@.gmail.com>
> > Newsgroups: microsoft.public.sqlserver.reportingsvcs
> > Subject: New export option
> > Date: Fri, 26 Oct 2007 17:12:18 -0000
> > Organization:http://groups.google.com
> > Hello Fellow RS
> > Has anyone ever heard of or tried adding to the report export list?
> > I've read through the BOL for report export options and searched the
> > web for advice. There is quite a bit of information folks have shared
> > on ways to export stored procedure results to a fixed length text
> > file. But I haven't found anything on exporting from a report to a
> > text file.
> > Is it was possible to export a report into a fixed length text file
> > from a Reporting Services website report... Hide quoted text -
> - Show quoted text -
Thanks for your response.
I'm beginning to think that SS Integration Services would be the best
bet to accomplish this task.
(And I did mean fixed width columns in the text file.)
Thanks again!|||On Oct 26, 12:09 pm, asflp <fpetrive...@.gmail.com> wrote:
> On Oct 26, 10:46 am, cal...@.online.microsoft.com (Chris Alton [MSFT])
> wrote:
>
>
> > The only text based export that Reporting Services does is CSV (Comma
> > Delimited). On adding a type to the export list you would have to write
> > your own rendering extension to transform the data in the report and that
> > isn't an easy task. If you look in the rsreportserver.config file you'll
> > see a <Render> section that contains all of the various rendering
> > extensions available to Reporting Services.
> > You can find more information about creating a rendering extension here:
> >http://msdn2.microsoft.com/en-us/library/ms153624.aspx
> > One last question. When you say "Fixed length text file" do you mean a
> > "fixed width" text file or an actual fixed size of the text file being
> > produced?
> > --
> > Chris Alton, Microsoft Corp.
> > SQL Server Developer Support Engineer
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > --
> > > From: asflp <fpetrive...@.gmail.com>
> > > Newsgroups: microsoft.public.sqlserver.reportingsvcs
> > > Subject: New export option
> > > Date: Fri, 26 Oct 2007 17:12:18 -0000
> > > Organization:http://groups.google.com
> > > Hello Fellow RS
> > > Has anyone ever heard of or tried adding to the report export list?
> > > I've read through the BOL for report export options and searched the
> > > web for advice. There is quite a bit of information folks have shared
> > > on ways to export stored procedure results to a fixed length text
> > > file. But I haven't found anything on exporting from a report to a
> > > text file.
> > > Is it was possible to export a report into a fixed length text file
> > > from a Reporting Services website report... Hide quoted text -
> > - Show quoted text -
> Thanks for your response.
> I'm beginning to think that SS Integration Services would be the best
> bet to accomplish this task.
> (And I did mean fixed width columns in the text file.)
> Thanks again!- Hide quoted text -
> - Show quoted text -
Just an add-on comment, I followed the link and I really can't tell
you why I didn't get to that part of BOL when I was reading about the
export options. BOL certainly is vast and interesting to navigate.|||You have to know the secret code word and hand shake to be able to really
search books online :)
It's always easy to find things when you know exactly what you are looking
for. If you search for "custom rendering extension" then you'll find that
section as the first result. If you have no clue that is what it is that
you are trying to do then searching for that stuff can be quite difficult.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> From: asflp <fpetrivelli@.gmail.com>
> Newsgroups: microsoft.public.sqlserver.reportingsvcs
> Subject: Re: New export option
> Date: Fri, 26 Oct 2007 19:25:57 -0000
> Organization: http://groups.google.com
> Lines: 65
> On Oct 26, 12:09 pm, asflp <fpetrive...@.gmail.com> wrote:
> > On Oct 26, 10:46 am, cal...@.online.microsoft.com (Chris Alton [MSFT])
> > wrote:
> >
> >
> >
> >
> >
> > > The only text based export that Reporting Services does is CSV (Comma
> > > Delimited). On adding a type to the export list you would have to
write
> > > your own rendering extension to transform the data in the report and
that
> > > isn't an easy task. If you look in the rsreportserver.config file
you'll
> > > see a <Render> section that contains all of the various rendering
> > > extensions available to Reporting Services.
> >
> > > You can find more information about creating a rendering extension
here:
> >
> > >http://msdn2.microsoft.com/en-us/library/ms153624.aspx
> >
> > > One last question. When you say "Fixed length text file" do you mean a
> > > "fixed width" text file or an actual fixed size of the text file being
> > > produced?
> > > --
> > > Chris Alton, Microsoft Corp.
> > > SQL Server Developer Support Engineer
> > > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > > --
> >
> > > > From: asflp <fpetrive...@.gmail.com>
> > > > Newsgroups: microsoft.public.sqlserver.reportingsvcs
> > > > Subject: New export option
> > > > Date: Fri, 26 Oct 2007 17:12:18 -0000
> > > > Organization:http://groups.google.com
> >
> > > > Hello Fellow RS
> >
> > > > Has anyone ever heard of or tried adding to the report export list?
> >
> > > > I've read through the BOL for report export options and searched the
> > > > web for advice. There is quite a bit of information folks have
shared
> > > > on ways to export stored procedure results to a fixed length text
> > > > file. But I haven't found anything on exporting from a report to a
> > > > text file.
> >
> > > > Is it was possible to export a report into a fixed length text file
> > > > from a Reporting Services website report... Hide quoted text -
> >
> > > - Show quoted text -
> >
> > Thanks for your response.
> >
> > I'm beginning to think that SS Integration Services would be the best
> > bet to accomplish this task.
> >
> > (And I did mean fixed width columns in the text file.)
> >
> > Thanks again!- Hide quoted text -
> >
> > - Show quoted text -
> Just an add-on comment, I followed the link and I really can't tell
> you why I didn't get to that part of BOL when I was reading about the
> export options. BOL certainly is vast and interesting to navigate.
>
>