Showing posts with label reporting. Show all posts
Showing posts with label reporting. Show all posts

Wednesday, March 28, 2012

remove deployed reports from server

How can I remove reports that have been deployed to my reporting services server?

Do you want just to delete the reports?

You can do it from internet explorer, type the reporting site then click Show details and then you can select and delete the objects that you want.

I hope it helps you.


|||using report manager, you can navigate to the respective report folder where you have deployed your reports. from there you can delete the deployed report.|||Thats simple enough. Thanks for the quick replies.

Monday, March 26, 2012

Remove "Select All" Options from Multi Select Parameter Dropdown

Hi All

I am using SQL Server 2005 with SP2. I have multi select parameter in the report. In SP2 reporting services gives Select All option in the drop down.

Is there any way I can remove that option from the list?

Thanks

No you can't remove it. It was removed by the MS team in SP1, but popular demand meant it was reinstated. The only way to get rid of it is to build your own UI.|||

FYI : the story is here

http://blogs.msdn.com/bwelcker/archive/2006/08/14/700189.aspx

and here

http://blogs.msdn.com/bimusings/archive/2007/04/09/the-curious-saga-of-select-all-and-multi-valued-parameters-in-reporting-services.aspx

... note that in the followup comments in the first one, Brian W does note that:

re: Rather Ripped (Select All in Service Pack 1)

Sunday, February 04, 2007 5:49 PM by bwelcker

I understand all of the angst around this decision. We will definitely make this configurable in the future, either on a server level or a per-report level.

... after which somebody responds "I prefer per-server" -- but I personally (LSN) would prefer per-report. So they really can't win, can they <g>. No, seriously, in this case they can't win unless they do both...

>L<

|||

Thanks for the reply everyone.

That answers my question.

Regards

Friday, March 23, 2012

Remote Web Report timing out

I've got an internal Reporting Server and I can access the reports directly
there with no problem.
I can generate a report with the WinForm without a problem as well.
What I'm trying to do is to use a second, public web server that has an ASPX
page containing the reportviewer control that connects to the internal web
server so we can implment the seucurity system used by the rest of the web
site.
I can open the report, which has an input parameter without a problem. When
I enter a parameter and attempt to generate the report, it connects to the
Report Server without a problem but then sits there, spinning the little
green arrow until it times out.
With profiler turned on I can see the exact same set of data calls being
made when the report is run on the report server, in the WinForm and in the
WebForm, the only difference being that it appears the WebForm never gets the
data back.
Any ideas?
--
Josef
http://www.reluctantdba.comOn Sep 13, 9:54 am, Josef Finsel
<JosefFin...@.discussions.microsoft.com> wrote:
> I've got an internal Reporting Server and I can access the reports directly
> there with no problem.
> I can generate a report with the WinForm without a problem as well.
> What I'm trying to do is to use a second, public web server that has an ASPX
> page containing the reportviewer control that connects to the internal web
> server so we can implment the seucurity system used by the rest of the web
> site.
> I can open the report, which has an input parameter without a problem. When
> I enter a parameter and attempt to generate the report, it connects to the
> Report Server without a problem but then sits there, spinning the little
> green arrow until it times out.
> With profiler turned on I can see the exact same set of data calls being
> made when the report is run on the report server, in the WinForm and in the
> WebForm, the only difference being that it appears the WebForm never gets the
> data back.
> Any ideas?
> --
> Josefhttp://www.reluctantdba.com
Normally hitting the web server will be slower if it is on another
machine/server. Also, communicating through IIS and a network takes
extra time. The only suggestion I have is to tune the query/stored
procedure that sources the report via the Database Engine Tuning
Advisor. This might give you a little performance improvement. Hope
this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Those are all good and valid points but it turns out that it was actually a
permissions issue.
I got it resolved and it works fine.
Thanks
--
Josef
http://www.reluctantdba.com
"EMartinez" wrote:
> On Sep 13, 9:54 am, Josef Finsel
> <JosefFin...@.discussions.microsoft.com> wrote:
> > I've got an internal Reporting Server and I can access the reports directly
> > there with no problem.
> >
> > I can generate a report with the WinForm without a problem as well.
> >
> > What I'm trying to do is to use a second, public web server that has an ASPX
> > page containing the reportviewer control that connects to the internal web
> > server so we can implment the seucurity system used by the rest of the web
> > site.
> >
> > I can open the report, which has an input parameter without a problem. When
> > I enter a parameter and attempt to generate the report, it connects to the
> > Report Server without a problem but then sits there, spinning the little
> > green arrow until it times out.
> >
> > With profiler turned on I can see the exact same set of data calls being
> > made when the report is run on the report server, in the WinForm and in the
> > WebForm, the only difference being that it appears the WebForm never gets the
> > data back.
> >
> > Any ideas?
> > --
> > Josefhttp://www.reluctantdba.com
>
> Normally hitting the web server will be slower if it is on another
> machine/server. Also, communicating through IIS and a network takes
> extra time. The only suggestion I have is to tune the query/stored
> procedure that sources the report via the Database Engine Tuning
> Advisor. This might give you a little performance improvement. Hope
> this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||On Sep 14, 4:02 pm, Josef Finsel
<JosefFin...@.discussions.microsoft.com> wrote:
> Those are all good and valid points but it turns out that it was actually a
> permissions issue.
> I got it resolved and it works fine.
> Thanks
> --
> Josefhttp://www.reluctantdba.com
> "EMartinez" wrote:
> > On Sep 13, 9:54 am, Josef Finsel
> > <JosefFin...@.discussions.microsoft.com> wrote:
> > > I've got an internal Reporting Server and I can access the reports directly
> > > there with no problem.
> > > I can generate a report with the WinForm without a problem as well.
> > > What I'm trying to do is to use a second, public web server that has an ASPX
> > > page containing the reportviewer control that connects to the internal web
> > > server so we can implment the seucurity system used by the rest of the web
> > > site.
> > > I can open the report, which has an input parameter without a problem. When
> > > I enter a parameter and attempt to generate the report, it connects to the
> > > Report Server without a problem but then sits there, spinning the little
> > > green arrow until it times out.
> > > With profiler turned on I can see the exact same set of data calls being
> > > made when the report is run on the report server, in the WinForm and in the
> > > WebForm, the only difference being that it appears the WebForm never gets the
> > > data back.
> > > Any ideas?
> > > --
> > > Josefhttp://www.reluctantdba.com
> > Normally hitting the web server will be slower if it is on another
> > machine/server. Also, communicating through IIS and a network takes
> > extra time. The only suggestion I have is to tune the query/stored
> > procedure that sources the report via the Database Engine Tuning
> > Advisor. This might give you a little performance improvement. Hope
> > this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
Glad you resolved the issue. Let me know if I can be of further
assistance.
Regards,
Enrique Martinez
Sr. Software Consultant

Tuesday, March 20, 2012

Remote Server into a named Instance of SQL Server 2005

We are setting up a database server with 2 instances of SQL Server 2005. One for the default and another for Reporting Service. I have them installed but when I try to a registration from another Server for the Reporting Service Instance I can not get in. I am using the sa userid and password, the same one that works when I am on the server but I get an error that says Remote Server connections may not be allowed. When I go to properties the Allow remote connections box is checked. Anyone know what else I need to do to get to the named instance?If you have another instance on the server it probably uses not the default port. If you have chosen another port than the default 1433 for the named instance, you should either start SQL Browser (which will handle request and will forward to the appropiate port on the server) or you directly name it within your connecting application by using the following syntax:

Servername\InstanceName,portnumber.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Monday, March 12, 2012

Remote Reporting Server

Can you have SQL 2005 reporting services installed on a front end web server
without a local SQL engine (i.e. the reports DB is on a remote engine).
Reporting is running and working on the remote back end server which has the
engine as well.
If this is so, can the back end server be SQL 2005 Enterprise SQL 64 bit,
and the front end web server be SQL 2005 Enterprise SQL 32 bitOn Feb 11, 2:06 pm, "John Hiebert" <johndhieb...@.hotmail.com> wrote:
> Can you have SQL 2005 reporting services installed on a front end web server
> without a local SQL engine (i.e. the reports DB is on a remote engine).
> Reporting is running and working on the remote back end server which has the
> engine as well.
> If this is so, can the back end server be SQL 2005 Enterprise SQL 64 bit,
> and the front end web server be SQL 2005 Enterprise SQL 32 bit
As long as your Report Manager and virtual directories for SSRS are on
the front-end server and the back-end server includes the ReportServer
and ReportServerTempDB databases, you should be fine with varying
editions of SQL Server. Of course, your SQL Server license for SSRS is
required in the location of your ReportServer and ReportServerTempDB
databases. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||We have a similar situation but we want SSRS to run on an internal web
server. So teh user has access only to the fron-end web server, and upon a
report request, he'll be forwarded to the internal server for report
processing. The question is how to configure the front-end IIS to run the
reports on the back end IIS.
Thanks,
Gilgamesh
"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:0946c772-2790-4993-ba61-b6cad04b4a79@.y5g2000hsf.googlegroups.com...
> On Feb 11, 2:06 pm, "John Hiebert" <johndhieb...@.hotmail.com> wrote:
>> Can you have SQL 2005 reporting services installed on a front end web
>> server
>> without a local SQL engine (i.e. the reports DB is on a remote engine).
>> Reporting is running and working on the remote back end server which has
>> the
>> engine as well.
>> If this is so, can the back end server be SQL 2005 Enterprise SQL 64 bit,
>> and the front end web server be SQL 2005 Enterprise SQL 32 bit
>
> As long as your Report Manager and virtual directories for SSRS are on
> the front-end server and the back-end server includes the ReportServer
> and ReportServerTempDB databases, you should be fine with varying
> editions of SQL Server. Of course, your SQL Server license for SSRS is
> required in the location of your ReportServer and ReportServerTempDB
> databases. Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant|||On Feb 13, 6:56 pm, "Gilgamesh" <Gilgamesh4E...@.aol.com> wrote:
> We have a similar situation but we want SSRS to run on an internal web
> server. So teh user has access only to the fron-end web server, and upon a
> report request, he'll be forwarded to the internal server for report
> processing. The question is how to configure the front-end IIS to run the
> reports on the back end IIS.
> Thanks,
> Gilgamesh
> "EMartinez" <emartinez...@.gmail.com> wrote in message
> news:0946c772-2790-4993-ba61-b6cad04b4a79@.y5g2000hsf.googlegroups.com...
> > On Feb 11, 2:06 pm, "John Hiebert" <johndhieb...@.hotmail.com> wrote:
> >> Can you have SQL 2005 reporting services installed on a front end web
> >> server
> >> without a local SQL engine (i.e. the reports DB is on a remote engine).
> >> Reporting is running and working on the remote back end server which has
> >> the
> >> engine as well.
> >> If this is so, can the back end server be SQL 2005 Enterprise SQL 64 bit,
> >> and the front end web server be SQL 2005 Enterprise SQL 32 bit
> > As long as your Report Manager and virtual directories for SSRS are on
> > the front-end server and the back-end server includes the ReportServer
> > and ReportServerTempDB databases, you should be fine with varying
> > editions of SQL Server. Of course, your SQL Server license for SSRS is
> > required in the location of your ReportServer and ReportServerTempDB
> > databases. Hope this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
The best way to accomplish this architecture is to utilize Render() as
part of the SSRS Web Service. So, have the front-end application be an
ASP.NET application that references the SSRS web service and the
reports from the back-end SSRS installation.
http://msdn2.microsoft.com/en-us/library/microsoft.wssux.reportingserviceswebservice.rsexecutionservice2005.reportexecutionservice.render.aspx
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

Wednesday, March 7, 2012

Remote Distributor question

sql2k sp3
BoxA Publisher.
BoxB Subscriber. To be used for reporting.
I want the processing drain of Replication to be done on
BoxB. So I was thinking of putting the Distributor on BoxB
and using a Push Subscription.
Do any of you gurus see any problems with my idea?
TIA, Chris?
Reporting services chews up a lot of cycles. You might find it better to
keep the distributor on the publisher.
The point you start to move the distributor off the publisher is when you
start to get significant locking on your distribution database.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:0a4701c46e74$e3ab90f0$a601280a@.phx.gbl...
> sql2k sp3
> BoxA Publisher.
> BoxB Subscriber. To be used for reporting.
> I want the processing drain of Replication to be done on
> BoxB. So I was thinking of putting the Distributor on BoxB
> and using a Push Subscription.
> Do any of you gurus see any problems with my idea?
> TIA, Chris?
|||>Reporting services chews up a lot of cycles.
My bad. I wont be using actual Reporting Services.
You might find it better to
>keep the distributor on the publisher.
>The point you start to move the distributor off the
publisher is when you
>start to get significant locking on your distribution
database.
>
Why is this? Why do people do it then?

>--Original Message--
>Reporting services chews up a lot of cycles. You might
find it better to
>keep the distributor on the publisher.
>The point you start to move the distributor off the
publisher is when you
>start to get significant locking on your distribution
database.
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>"ChrisR" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:0a4701c46e74$e3ab90f0$a601280a@.phx.gbl...
BoxB
>
>.
>
|||Well, most people do it to reduce the load on the Publisher. The question is
when should you do it, and there is no real rule of thumb, at least as far
as I am aware.
The deciding factor for me is when you experience locking in your
distribution database.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:0c4201c46e8a$e7dd03a0$a601280a@.phx.gbl...[vbcol=seagreen]
> My bad. I wont be using actual Reporting Services.
> You might find it better to
> publisher is when you
> database.
> Why is this? Why do people do it then?
> find it better to
> publisher is when you
> database.
> message
> BoxB