I installed SQL Server 2019 Enterprise edition (with custom instance name, not default one) with CU8 followed by SQL Server Reporting Services. But when I am trying to connect to the SQL Server Reporting Server in SQL Server Management Studio, it shows default instance name i.e. SSRS and it doesn't connect.
However, I am able to connect to the database engine server.
For the same reason I am not able to install Reporting Services Role in my primary site server as Reporting server instance name doesn't get populated. However I am not facing this issue in SQL Server 2012 Enterprise as SQL Server Reporting Services .exe file doesn't come as a separate file in SQL Server 2012 Enterprise and it is installed with SQL Server itself.
Related
I am trying to migrate a database in-place (same PC) from SQL Server 2008 R2 Express to SQL Server 2019 Express, by using DMA (Database Migration Assistant). But I cannot connect to the target server (2008) during the "Assessment" task.
I have installed SQL Server 2019 as coexisting installation assigning the following instance names:
MSSQLSERVER (default name assigned during SQL Server 2008 R2 installation)
MSSQLSERVER2019 (different instance name assigned during SQL Server 2019 installation)
The PC is named DESKTOP1 and this results into the following server names:
DESKTOP1 for SQL Server 2008 R2
DESKTOP1\MSSQLSERVER2019 for SQL Server 2019
Both the server names work fine and I can normally connect to the servers by means of Management Studio.
The weird behaviour is that during the database assessment task, I couldn't connect to the source database server (DESKTOP1). Then I tried to go directly to the "Migration" task and I was able to connect. After this I went back to the "Assessment" task and (kind of magic) I was able to connect to the server DESKTOP1.
Do you have any clue about this issue? It looks like during Migration task there is something that enable the server connection.
Thank you!
I have SQL reporting service running on SQL 2014 version while reporting database is configured on SQL 2008R2. I am planning to migrate SQL 2008R2 to SQL 2016 so I'll move report server database to new 2016 server while reporting service will be continue to run on SQL 2014. Would there be any issue/concerns if report server database is running on SQL 2016 while reporting service is running SQL 2014?
Following document for SQL Server 2014: Create a Report Server Database states that it is not supported.
SQL Server is used to host the report server databases. The SQL Server Database Engine instance can be a local or remote instance. The following are the supported versions of SQL Server Database Engine that can be used to host the report server databases:
SQL Server 2014
SQL Server 2012
SQL Server 2008 R2
SQL Server 2008
SQL Server 2005
I am setting up a new SQL Server 2014 Enterprise Reporting Services instance on a Windows Server 2012 R2 server.
In Reporting Services Configuration Manager, when I select the SQL Server instance where I want to setup a new report database, the error message below is shown:
The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.
Error:
The SQL Server instance where I intend to setup the report database runs SQL Server 2014 Developer Edition build 12.0.4422 (which is displayed in Management Studio and ##version) and the SQL Server instance where I am configuring Reporting Services runs also MSQL 2014 build 12.0.4422 as displayed in Reporting Services Configuration Management - but Enterprise Edition (I've just installed SQL Server Cumulative Update 2 from https://support.microsoft.com/en-us/kb/3075950).
If I select an instance which runs SQL Server 2008 R2 Enterprise Edition build 10.50.4260 instead, the error is not shown and the setup proceeds correctly - but unfortunately this is not the instance where the report database should be.
What am I missing here? How can I solve this issue?
Thanks in advance,
Cristhian.
This behavior is correct. The reporting services database is supported on a wide range of versions.
You are not allowed to use a production reporting services against a developer version database. (Why would you want to!). You can either use a developer edition of reporting services, or an enterprise database.
I am new to AppHarbour and I am trying to deploy an ASP.NET MVC 3 Web application here. I have successfully deployed the web application.
Now I want to run some sql scripts on the database provided.
For which I have followed the following steps...
Step 1 :
Step 2 :
Step 3 :
Now here I get the server name, username and password as well as the database name, but !
When I try connecting to this database using SQL Server Management Studio I just cannot connect to it.
I always get the following error message
TITLE: Connect to Server
Cannot connect to e2f7c78d*********b9.sqlserver.sequelizer.com.
ADDITIONAL INFORMATION:
This version of Microsoft SQL Server Management Studio can only be used to connect to SQL Server 2000 and SQL Server 2005 servers. (ConnectionDlg)
Please can some one help me on this. Thanks
Appharbor uses Sql Server 2008 R2 (Microsoft SQL Server Express Edition with Advanced Services, version 10.50.1600.1). Use Microsoft SQL Server Management Studio 2008 R2 version or newer and it should work.
I'm opening up SQL Server 2008 R2 Management Studio.
When I connect to my database server, it says the version is 9.0.2047. But when I connect to my analysis server and report server, they are both version 10.50.1600.1.
How can I change my database server so that it is running version 10.50.1600.1?
In the SSMS Object Explorer, from the "Connect dropdown > Database Engine..." item, you can choose from all your available database servers.
It seems like you have different versions of SQL Server installed alongside each other.
Uninstall SQL Server 2005, and install SQL Server 2008 R2.
Here's a nice website with versions for you.