getting confused here. I'm trying to install a second instance of reporting service sql server 2008 r2. Now does it mean I need to install a second instance of sql server or can i use the existing sql server instance to create anothe reportserver database?
for 2005 I know that you would have to run setup again to install another instance. I am not sure if they changed it in later versions, although I believe it is still the same.
See "Installing Multiple Instances of Reporting Services" and "Multiple Reporting Services instances on one machine". If you want to share one database, consider a scale-out deployment.
No, you don't have to install sql engine instance. You start an installation from SQL Installation Center and check only Reporting from features.
Related
I've downloaded SQL Server 2016 standard edition trial along with SSDT in order to test what one can do with a standard edition in SSIS, SSRS, and SSAS.
I also wanted to know whether standard version's SSISDB logging capabilities differs from the one in Enterprise. For this I wanted to create an SSISDB catalog under Integration Services Catalogs in SSMS.
When I try to do this, however, I get the error saying that
The catalog backup file 'C:\Program Files\Microsoft SQL Server\130\DTS\binn\SSISDBBackup.bak could not be accessed. Make sure the database file exists, and the SQL server service account is able to access it
From googling this issue it appears as this message shows up whenever someone doesn't have SSIS installed, but I have SSIS on the machine, I've even made a small Project and executed it from within SSIS without any issues just to verify.
I have set this up on localhost where I am the admin. Does anyone have any ideas why this won't work?
Regards,
Cenderze
To check if SSIS installed, open Sql Server Configuration Manager, in the SQL Server Services, is something like 'SQL Server Integration Services 13.0' running?
Experienced this error message on MS SQL Server 2017.
Resolved by launching MS SQL Server 2017 install media, added Integration Services feature.
After successful installation, when back into SSMS, right-click on Integration Services Catalog for Create Catalog... option.
You will be asked for an encryption password to create the new SSISDB.
Hope this helps!
I faced with this error when I used lower version of SSMS than SSIS. Check if you use proper version of SQL Management Studio.
You need to go back to the SQL Server installation and check the integration services checkbox.
The issue is because SQL Integration services is not installed properly with the existing SQL Server you are using.
you can check if SQL Integration services are installed or not by,
Opening --> SQL Server Configuration Manager--> SQL Server Services --> Check if "SQL Server Integeration Services is there"
if its there and if you still get the same issue try re-installing.
Else install the SQL Integration services to your existing SQL Server.
The detailed step to installation is given in this link : https://www.mssqltips.com/sqlservertip/6635/install-ssis/
hope this helps !!
Is it possible to do an in place upgrade of you SQL server edition, (for example upgrade 2012 Express to Standard), when it is running and used by a team foundation server 2015 instance? Will this need extra configuration or will we need to detach/attach the team project collections first?
I can't find any information about how to do this. It is only stated how to upgrade the team foundation server itself, or that it is no problem to do edition upgrades of sql server, but not the combination of the two.
Yes
You can:
Use the TFSServiceControl quiesce command to turn off your servers services.
Upgrade SQL Server in place following SQL Servers Instructions
Use the TFSServiceControl unquiesce command to turn on your servers services.
https://www.visualstudio.com/en-us/docs/setup-admin/tfs/command-line/tfsservicecontrol-cmd
As far as I can remember:
No.
You will need to detach your collection.
Make sure the SQL Server version is supported by your TFS Version
I am using LocalDB for DB testing but my dev PC seems to have SQLServer 2005, 2008 and 2012 installed/running - I am not sure exactly which are running as there are so many services and I have 3 versions of SQLServer Configuration Manager installed!
I want to disable all DB engines other than LocalDB and am wondering if I just turn all the SQLServer services to off, start-mode = manual, this will achieve my aim... or will also turn off LocalDB?
My suspicion is that localdb is a database that is hosted on one of the instances you're running on your machine. If you know the instance name (e.g. SQLExpress, SYSARCH, SYSARCH1, or the default [and therefore unnamed] instance) you connect to when working with localdb, yes, you can set the other database instances to either manual start or disabled so they will not auto-start after a reboot. Another approach is to use the services.msc snap-in, but know that this will list all services on the machine instead of only the SQL Server services.
I'm currently using Postgresql Database 9.1 (running Adempiere)
I've been using SQL Server Data Tools on my computer and connecting directly to the server computer to create reports.
Now i want to install the Reporting Services aspect on the computer server so that other users can access the reports through the Report Manager. And also so that it can automatically deliver reports to the users
Is it possible to install SQL Server 2008 in the same computer as Postgresql? And if so, what are the steps that i need to take?
Thanks!
Yes, this is possible to install.
and You should not run into any problems, both servers run on different ports (by default) so both should run happily side by side.
But I dont think its supported, so you won't find any instructions.
Hope it helps.
When I try to install the Reporting Services on a second node of a failover cluster, I get the following error message:
Existing clustered or cluster-prepared instance failed. The instance selected for installation is already installed and clustered on node 2.
But, we never installed it before. Does anyone have any ideas? This is on Windows 2008 server 64-bit.
Just one thing though. You have to install Reporting Services using the Enterprise Edition media and to avoid doing all kinds of nasty stuff to the Licensing the fail-over cluster also have to be Enterprise Edition.
If you try to do this using the SQL Server Standard media you will not be able to install SSRS to a "Shared Database" and the encryption information in the database created by instance #1 will be mercilessly blasted into oblivion.
This will result in instance 1 of SSRS not working while instance 2 (on the second server) is working. Trying to fix this will only flip the situation.
Personally i find this to be quite the bummer from Microsoft since it practically means that you have to weigh the cost of Enterprise Edition against HA-enabling Reporting Services.
So basically, you have to acquire Enterprise Edition if you do not want your Reporting Services to be the Single Point of Failure.
Apparently, SQL Server can be installed on each node on a failover cluster. The caveat is that it must be two separate installations with two different instance names. You can, however, share the same report server database. Please read this article for more information on deploying Reporting Services.
http://msdn.microsoft.com/en-us/library/ms159114.aspx
Consider this article on SSRS scale out process. Install the shared report server database on the cluster. Then install reporting services to use the shared database. Reporting services will not failover, but the database will.
This is an option to failover IIS: http://support.microsoft.com/kb/970759