September 17, 2014 at 6:02 pm
I am working on a side by side upgrade and migrade of a reporting server to a new server from 2008r2 to 2012. Standard edition.
I will call it ServerA- old server, ServerB - new server.
Both server has db engine and reporting service installed. Standalone and native mode.
So far I have taken these steps:
1. Do all the backups of database and some configuration files and encryption key.
2. Installed SQL 2012 on ServerB and restore ReportServer and ReportServertempdb from ServerA backup to ServerB.
3. In reporting server configuration manager of ServerB, databse setup page, change database and reconnect.
4. restore encryption key from ServerA to ServerB.
5. I open the report server manager website, it gives error The feature: "Scale-out deployment" is not supported in this edition of Reporting Services, I go the the reportsever databse and delete the key that is associated with the oldServerName.
Everything works fine so far.
Now we have a plan to swap the server name this weekend.
That means I will change the servername of ServerB back to ServerA, and take the old ServerA offline.
This way the developers have no need to change the connection string that in their applications.
But my question comes:
Steps I am going to do:
1, Take offline ServerA. Network admin will rename ServerB to ServerA.
I will then change SQL server name by using Sp_dropServer and Sp_addServer .
2. Then open Reporting server configuration tool, database setup page, -change databse button from there to change servername.
My question is next step:
In the scale -out deployment, will servername change from ServerB to ServerA automatically? or will it have both ServerA and ServerB there?
If both, I will have to remove one. Which one should I remove?
September 17, 2014 at 8:07 pm
Not sure about your final question on the naming but make sure that you change the IP address of the new server to that of the old server, as well. Lot's of folks will say that you don't need to do that and they'd be right except for any code that has unfortunate connection by IP address.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 18, 2014 at 10:01 am
Yes, we will change IP too.
My questions is about after rename computer what will show on the scale-out deployment screen, will that show both server names. or only name ServerB.
How can I change it there to Server A?
We are using standard edition,only one server can show up there and we only need the ServerA shows up there.
This is hard to prepare for I have to wait until the server swap time. I can see the result only at that time.
But thought someone here may have done this before or know exactly the scale out screen and key table work?
Thanks
September 18, 2014 at 11:20 am
More info about my question:
It is easy to rename SQL server with only DB engine and/or SSIS installed, for reporting server it is a little tricky.
Especially on the Scale-out deployment screen, which is not well documented if having multiple servers showing there. We only need one server to show there, so no need to use Enterprise edition.
Because for now I cannot test it , I have to see what will show on that screen exactly when we do the server swap and rename time on Friday. Two servers or only one?
I know a couple of ways to remove the server from that screen: but for this case, I wonder should I delete the ServerB on the screen, or delete ServerA and rename ServerB item in the reportserver.dbo.keys table? the installationID part confuse me.
Just thought if someone in this forum have experience of that or know exactly the scale out deployment and table/schema work?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply