Does anyone know if it is possible to install SQL 2000 Reporting Services Server side by side with SQL 2005 Reporting Services Server?
The Reports and ReportServer virual directories are both virtual directories in the default website and they use different .net frameworks. Is this even allowed? Do I need to create a new website to support one of the two engines?
Thanks!
The answer is YES. You must keep the SQL Server 2000 version as the default instance, and the SQL Server 2005 version as a named instance. Also,
The virtual directories must be unique
for each report server and Report
Manager instance.
You can use the same Web site for all
virtual directories. However, you
should create a separate application
pool for the SQL Server 2005 report
server and Report Manager
applications.
Source
Related
I have an operational SQL VM in Azure. How do I provision Azure to see it under SQL Databases and provide it as an option when creating something like Mobile Services?
That is not possible. The SQL Database feature is a service and, while it does run a highly compatible SQL Server environment, it is not the same as the SQL Server you would install on premises, or on a hosted virtual machine. There is not a way to "register" an existing SQL Server database, either in or outside of Azure, as a SQL Database instance.
If you want to have the Mobile Services system pointing to a SQL Server instance that is NOT a SQL Database I do not believe that is possible either. You can post a suggestion to the http://www.mygreatwindowsazureidea.com/forums/34192-general-feedback- site. The product group does monitor this and take it into account during product backlog sessions.
Is it possible to install SSRS and SQL Server database on separate servers, or should these two be installed on the same server?
Thanks
In order to have Reporting Services on your application server, you would have to use a SQL-Server license. You can install just the Reporting Services section of SQLServer, but it is still technically part of the SQL Server application and requires a license for use on that processor(s).
So yes, you can install it on another server.
Yes, you can install only the advanced services, but that still counts as full server., so it requires a full license.
Yes, you can install an Express Edition (with advanced services) on another server for free.
But... the express edition SSRS can't access a non-localhost database (technical limitations of express & web edition).
You can try to circumvent that with linked-servers, but you need to duplicate every used stored procedure, view, table etc., so it's an impractical mess.
The answer to your question is thus: Technically, yes - but actually NO, not without another license.
That extra-installation is gonna cost USD 1'000+ per month.
Yes, you can install SSRS and a SQL Server database on different servers. While the default installation tries to install both, you can select to install them separately.
MSDN links:
Considerations for Installing Reporting Services
Installing SQL Server Reporting Services
From MSDN article Considerations for Installing Reporting Services:
Select Database Engine Services in the Feature Selection page to host
the report server databases. Reporting Services requires a local or
remote instance of SQL Server 2005 or SQL Server 2008 Database Engine
to host the report server databases. If you install an instance of the
Database Engine concurrently with Reporting Services, you can
eliminate a post-Setup task by installing the default configuration,
which creates and configures the report server databases
automatically. In addition to hosting the report server databases, SQL
Server relational databases can also be a source of data for reports
and models.
You could install SSRS in a new server, but to do so you would need a new license for this other server.
From Microsoft SQL Server 2014 Licensing Guide:
"The software components of a single SQL Server 2014 license cannot be separated for use in more than one OSE. If these components are running on a server other than the main database server, then an additional license is required for each additional OSE in which they are installed. For example, if the SQL Server DB is deployed in one OSE and SQL Server RS is deployed in another, both OSEs must be fully licensed for SQL Server 2014 accordingly."
Link to download the guide:
http://go.microsoft.com/fwlink/?LinkId=230678
I'm trying to set up Microsoft SQL Server Reporting Services. I open the Reporting Services Configuration Manager, and it asks for a Server name. Thing is, I don't know the server name, because as far as I know haven't set a report server up yet. So, how do you set one up for Microsoft SQL Server 2008 R2? There seems to be plenty of documentation out there how to configure one, but not how to install a new instance.
Server name is the name of the database server. You first have to install SQL server on the server you want to use and then install Reporting Services. When installing SSRS you specify the name of the SQL Server.
It does not have to be on the same machine of course.
I am going to use SSRS to generate report for my website.
Scenario:
I have 2 servers, Application server & Database Server.
I want to have reports(.rdl files) sitting on Application server(IIS) accessing data on SQL server(Database Server)
In order to fulfil these requirement I require to install SQL server 2k5 on my Application server just for having SQL server reporting service. So I am just waisting one of licence of SQL server by installing that on Application server.
Is anyone having any idea how to install only reporting service with SQL server 2k5??
In order to have Reporting Services on your Application server, you would have to use a SQL license. You can install just the Reporting Services section of SQL Server, but it is still technically part of the SQL Server application and requires a license for use on that processor(s).If that is a huge issue, then I would have to recommend keeping the Reporting Services section installed with the rest of the database installation on your Data server.
http://www.microsoft.com/sql/prodinfo/previousversions/rs/howtolicensers.mspx
The server components of SQL Server 2000 Reporting Services include the Report Server and the Report Server Database. The Report Server processes and renders reports, and handles scheduled events and report delivery. The Report Server Database stores report definitions, report metadata, subscription information, and so on. Each Report Server requires either a local or remote connection to a Report Server Database. To use any of these components, each computer on which the Report Server and the Report Server Database are installed must have a valid SQL Server 2000 license.
You could install SQL Server Express on the application server.
It's free, and there's an edition which comes with Reporting Services.
In comparison with the "real" editions, SQL Server Express Edition is limited concerning how much CPU and RAM it can use, but it will probably be fast enough to run your reports.
blatantly incorrect. You do not need a SQL Server license to use SQL Server Reporting Services, you can use SQL Server Express edition. I've use SQL Server Express Edition in addition to linked servers-- to query stuff on -ANY- database server. And it works great.
SSRS is a great platform, I Just hate it when people run around saying that you NEED a license to use it. I'll bet that guy works for Oracle corp!
You do have an alternative. You can embed reports directly into your code projects in .Net. In this case the report runs through the Microsoft.Reporting.WinForms and Microsoft.Reporting.WebForms namespaces, ReportViewer object. Each report will have a ".rdlc" extension instead of ".rdl", though the two files types are actually equivalent. There is an ASP.Net version of the ReportViewer that allows you to integrate these reports into your website. You just need to drag the ReportViewer control from the toolbox into your website to configure it. For more information, see the MSDN overview of ReportViewer Controls.
If you dont want to use a whole license you can always use reportviewer. Just so I dont put too much answer out here, the big site for this is gotreportviewer.com.
The reportviewer control does the work of the reporting services server when it comes to the generation of reports. RDL files are like xml files and dont do much until they are interpreted. If you embed the reportviewer in your application on the web the work will be done on the user side. It is simialar to microsofts xps format, it has to be interpreted.
If you don't want to create an application for your reports the new version of sql2008 with advanced controls allows you to install a free version of reporting services. It doesnt have all of the goodies but it works for simple deployments.
I need to transfer a database from a SQL Server instance test server to a production environment that is clustered. But SQL Server doesn't allow you to use backup/restore to do it from single instance to cluster. I'm talking about a Microsoft CRM complex database here.
Your help is greatly appreciated.
Have a look at the Microsoft SQL Server Database Publishing Wizard:
SQL Server Database Publishing Wizard
enables the deployment of SQL Server
databases into a hosted environment on
either a SQL Server 2000 or 2005
server. It generates a single SQL
script file which can be used to
recreate a database (both schema and
data) in a shared hosting environment
where the only connectivity to a
server is through a web-based control
panel with a script execution window.
If supported by the hosting service
provider, the Database Publishing
Wizard can also directly upload
databases to servers located at the
shared hosting provider.
Optionally, SQL Server Database
Publishing Wizard can integrate
directly into Visual Studio 2005
and/or Visual Web Developer 2005
allowing easy publishing of databases
from within the development
environment.
You don't have to use the server-side piece; the client-side 'create a script' piece is generally enough.