Push V/S Pull

I believe I have read this before, and apologize for being redundant...
If you have a new server that will be dedicated to reporting, it is more efficient & faster to make this server the Distributor & do a PULL from the production database?
I am pretty sure I have a pretty good understanding of changes being replicated & pushed, but can you help me understand why Pull would be the better option.
Sorry for being thick, I have been reading & reading, and it just isn't sticking...
Thanx!
JLS,
The Distribution Agent can consume significant amounts of memory and CPU cycles, so using pull (or anonymous) subscriptions can increase performance by moving agent processing from the distributor to the subscriber.
The Log Reader Agent writes commands to the distribution database and if you have a remote distributor you also gain by reducing disk I/O on hte production server. Also, the cleanup tasks that are run as a maintenance activity on the distribution database can become expensive and involve significant disk activity.
HTH,
Paul Ibison
(The ONLY sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanx Paul.
I am having an issue of a stored procedure inside a Crystal Report running seamlessly inside my ERP system, faster than my replication records are present in my reporting database.
I am hoping if I change to a PULL subscription with the Distributor being the box where the Reporting database resides, that this problem will be resolved.
I don't want to put a delay into the sp, that would be like shooting myself in the foot. The whole reason for the reporting database is to speed things up on both sides, logically the ERP will run faster once the reports execute on a different box, and this should also be true for the reports, since they will have their own servers.
Any other suggestions for me? I have read everything I can get my hands on.
I'm down to thinking about having 2 separate ODBC drivers, one for the seamless shipping reports that are executing so fast to continue to process on the production db, and all other reports execute on the reporting server & db. But I would really rather have all reports happening on the reporting server & db if at all possible....
"(The ONLY sql server 2000 replication book:" but it's still not available......
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:%23tJzWqdlEHA.3392@.TK2MSFTNGP14.phx.gbl...
JLS,
The Distribution Agent can consume significant amounts of memory and CPU cycles, so using pull (or anonymous) subscriptions can increase performance by moving agent processing from the distributor to the subscriber.
The Log Reader Agent writes commands to the distribution database and if you have a remote distributor you also gain by reducing disk I/O on hte production server. Also, the cleanup tasks that are run as a maintenance activity on the distribution database can become expensive and involve significant disk activity.
HTH,
Paul Ibison
(The ONLY sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||JLS,
I'd definitely recommend this article for performance optimization hints: http://www.microsoft.com/technet/pro.../tranrepl.mspx
In particular, have a look at the sections on the Log Reader Agent Properties and the Distribution Agent Properties.
The most important one in most cases is POLLINGINTERVAL (both agents) in order to reduce the latency to a minimum.
HTH,
Paul Ibison
|||That helps a great deal, Thanx!
One more quick question....
Which table holds the commands to be replicated?
For example, yesterday I had an issue with a duplicate record, and I wanted to clear the command "Call MS_Repl_delete....."
I know I have done this before, but I can't recall what table I cleared it from the last time.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:ObEfrdelEHA.2884@.TK2MSFTNGP09.phx.gbl...
JLS,
I'd definitely recommend this article for performance optimization hints: http://www.microsoft.com/technet/pro.../tranrepl.mspx
In particular, have a look at the sections on the Log Reader Agent Properties and the Distribution Agent Properties.
The most important one in most cases is POLLINGINTERVAL (both agents) in order to reduce the latency to a minimum.
HTH,
Paul Ibison
|||JLS,
select * from distribution.dbo.MSrepl_commands
or
sp_browsereplcmds
Cheers,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Pulling reports from Reporting server

I have reports posted to my server and need to edit them. My issue is the original rdl has been "misplaced". I do not have a model built for this server so I cannot use the built in report builder. Is there a way to "download" from the reporting server?Yes. Using Report Manager, If you click on the "properties" of the report and go to the "general" tab, there is an "edit" button right below "Report Definition". This should prompt an edit/save dialog box that will let you download the report if you have the appropriate permissions.

Publishing reports to different versions

I have Visual Studio 2005 and Reporting Services 2005 on my client development machine.

I want to publish the reports to an SQL Server 2000 with Reporting Services 2000 server, is this possible?

I get the following error message:

The report definition is not valid. Please verify that the report definition uses the current report definition namespace (i.e. ‘http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition’). (rsNotACurrentReportDefinition) Get Online Help

Thanks.

Bruce

Unfortunately, you will not be able to use the 2005 report designer to publish directly to a 2000 report server. This is due to the fact that the RDL's (Report Definitions) created are different between Report Server versions. You can however use the 2000 report designer to publish to a 2005 server, as it support auto-upgrade of the reports.

Thanks, Jon

Published wish list?

Greetings,
Is there a published wish-list or a prioritised "future features" list for
Reporting Services?
Such a list would help me avoid asking if a non-existent feature has been
implemented and (maybe) give me some idea of when a particular desirable
feature may become available...
--
Regards,
Neale NOONSorry, we don't publish the wishlist. (Even if we did, it wouldn't include
current plans/priorities since those are subject to change).
--
This post is provided 'AS IS' with no warranties, and confers no rights. All
rights reserved. Some assembly required. Batteries not included. Your
mileage may vary. Objects in mirror may be closer than they appear. No user
serviceable parts inside. Opening cover voids warranty. Keep out of reach of
children under 3.
"noonie" <noonie1155@.hotmail.com> wrote in message
news:Osahq$JdEHA.1424@.tk2msftngp13.phx.gbl...
> Greetings,
> Is there a published wish-list or a prioritised "future features" list for
> Reporting Services?
> Such a list would help me avoid asking if a non-existent feature has been
> implemented and (maybe) give me some idea of when a particular desirable
> feature may become available...
> --
> Regards,
> Neale NOON
>|||Thanks Chris,
"Chris Hays [MSFT]" <chays@.online.microsoft.com> wrote in message
news:O2PeLbMdEHA.4048@.TK2MSFTNGP12.phx.gbl...
> Sorry, we don't publish the wishlist. (Even if we did, it wouldn't
include
> current plans/priorities since those are subject to change).
Then is this the appropriate forum to "make a wish"?
1. Support for more CSS properties in RDL (background-attachment for
background images would be helpful)
2. More reliable column name discovery in the dataset designer when using
stored procedures (I want to reuse some stored procedures designed for
another application but they potentially return more than one data set and
the designer only identifies the column names of the first potential table
even after running the query with the correct parameters to select the right
data for the second potential table)
3. More rendering choices in the export report function. (RTF is high on my
list)
> "noonie" <noonie1155@.hotmail.com> wrote in message
> news:Osahq$JdEHA.1424@.tk2msftngp13.phx.gbl...
> > Greetings,
> >
> > Is there a published wish-list or a prioritised "future features" list
for
> > Reporting Services?
> >
> > Such a list would help me avoid asking if a non-existent feature has
been
> > implemented and (maybe) give me some idea of when a particular desirable
> > feature may become available...
--
Regards,
Neale NOON|||Anytime you'd like to see something added to SQL Server, send email to
sqlwish@.microsoft.com. Those emails go directly into the mailboxes of the
folks making the decisions and are also logged into an internal database so
we can track them. You probably won't get a personal response, just an
automatic one, but these really are listened to and acted upon. Trust me.
:-)
--
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"noonie" <noonie1155@.hotmail.com> wrote in message
news:uKLIJfOdEHA.2352@.TK2MSFTNGP09.phx.gbl...
> Thanks Chris,
> "Chris Hays [MSFT]" <chays@.online.microsoft.com> wrote in message
> news:O2PeLbMdEHA.4048@.TK2MSFTNGP12.phx.gbl...
>> Sorry, we don't publish the wishlist. (Even if we did, it wouldn't
> include
>> current plans/priorities since those are subject to change).
> Then is this the appropriate forum to "make a wish"?
> 1. Support for more CSS properties in RDL (background-attachment for
> background images would be helpful)
> 2. More reliable column name discovery in the dataset designer when using
> stored procedures (I want to reuse some stored procedures designed for
> another application but they potentially return more than one data set and
> the designer only identifies the column names of the first potential table
> even after running the query with the correct parameters to select the
> right
> data for the second potential table)
> 3. More rendering choices in the export report function. (RTF is high on
> my
> list)
>> "noonie" <noonie1155@.hotmail.com> wrote in message
>> news:Osahq$JdEHA.1424@.tk2msftngp13.phx.gbl...
>> > Greetings,
>> >
>> > Is there a published wish-list or a prioritised "future features" list
> for
>> > Reporting Services?
>> >
>> > Such a list would help me avoid asking if a non-existent feature has
> been
>> > implemented and (maybe) give me some idea of when a particular
>> > desirable
>> > feature may become available...
> --
> Regards,
> Neale NOON
>|||Thanks Stephen :-)
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:uftM3IadEHA.3380@.TK2MSFTNGP12.phx.gbl...
> Anytime you'd like to see something added to SQL Server, send email to
> sqlwish@.microsoft.com. Those emails go directly into the mailboxes of the
> folks making the decisions and are also logged into an internal database
so
> we can track them. You probably won't get a personal response, just an
> automatic one, but these really are listened to and acted upon. Trust me.
> :-)
> --
> Sincerely,
> Stephen Dybing
--
Regards,
Neale NOON

Publish between servers

Is it possible to publish a report from a DEV reporting server to a
PRODUCTION reporting server?
We would like our developer to deploy to the DEV server and then
someone publish it to production
gertYou can use RSScripter to do this
http://www.sqldbatips.com/showarticle.asp?ID=62
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Gert Conradie" <gert.conradie@.gmail.com> wrote in message
news:1125402536.289327.24680@.f14g2000cwb.googlegroups.com...
> Is it possible to publish a report from a DEV reporting server to a
> PRODUCTION reporting server?
> We would like our developer to deploy to the DEV server and then
> someone publish it to production
> gert
>|||Perfect, really really handy!
Wish list: Specify destination server so that one dont have to run the
bat file in two step process. But still as it is - really hande.
Thanks.
gert
Jasper Smith wrote:
> You can use RSScripter to do this
> http://www.sqldbatips.com/showarticle.asp?ID=62
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Gert Conradie" <gert.conradie@.gmail.com> wrote in message
> news:1125402536.289327.24680@.f14g2000cwb.googlegroups.com...
> > Is it possible to publish a report from a DEV reporting server to a
> > PRODUCTION reporting server?
> >
> > We would like our developer to deploy to the DEV server and then
> > someone publish it to production
> >
> > gert
> >

Publish A Report Services Report to SharePoint

OK... I'm running out of things to try.

I have SQL Server 2005 SP2 installed and Reporting Services Addin configured. I am trying to publish a report from BIDS to SharePoint... but a box continues to pop up asking me for credencials.

What am I doing wrong? I have reviewed all the web.config files as per an earlier post referenced, but I only see one entry in the config file for the location tag. However, I did see this tag in two config files... not certain if that is something I should be concerned with?

I'd really like to just get a sample report up on the Sharepoint Server so I can move forward.

Can anyone help?

You can always just upload the .RDL file directly into SharePoint using the SharePoint web UI. When RS integrates with SharePoint, we tell SharePoint to handle .RDL files as Report Server items, and it doesn't really matter whether they get into SharePoint through Report Designer, or through SharePoint web UI.

I'm afraid I can't help with the Report Designer issue. I'll pass this on to someone who might know about it.

|||Please check Inetpub\wwwroot\wss\VirtualDirectories\80\web.config|||

What am I looking for when I go to Inetpub\wwwroot\wss\VirtualDirectories\80\web.config?

It does have one entry for location path=" _vti_bin...." as previously mentioned, a number of the web config files have this entry in it... but only once per file.

And just to clarify... I am using BIDS trying to deploy the report. The version of Visual Studio is: 8.0.50727.42.

|||I did that and surprisingly it worked... how does the report connect to the database? I did not upload or create a datasource? Well... actually I had manually created one in SharePoint in another library, but subsequently deleted it. The report still runs?|||Actually... I'll answer my own question... the first report used a custom data source... so that is why it worked. The second used a shared data source... it failed until I created the shared datasource|||

I've been running into this, too. Brian Welcker's blog solved it.

http://blogs.msdn.com/bimusings/archive/2007/02/07/reporting-services-login-dialog-appears-when-deploying-to-moss-wss.aspx