November 15, 2017 at 3:11 pm
Hello,
Hoping somebody can help. We're migrating a very large vendor application to a 4-node AlwaysOn cluster. One node will be the reporting and analytics environment and will include AlwaysOn replicas of the prod OLTP databases. During the migration (this weekend) we'll be renaming the Windows server from "ServerHostnameNEW" to "ServerHostname." ServerHostname is the current environment hostname and this architectural design decision was made in consideration of the user base, so they would not have to repoint all their reporting and analytics tools.
I'm not sure what needs to happen with the SSAS server installed on "ServerHostnameNEW". I came across a Technet article stating you can rename an SSAS "instance" using asinstancerename.exe. I'm not sure if the Technet article refers to to the SQL Server instance name, or the windows hostname as the article keeps referring to this as an "instance" name change.
Additionally, Technet says asinstancerename.exe is not supported in a clustered environment. Frankly I'm a little confused. Are we talking all clustered environments or an active/passive clustered environment? There are multiple clustering options in SQL 2014? If renaming an SSAS install on an AlwaysOn node can not be accomplished with asinstancerename.exe, then how do I rename the SSAS installed there, or do I need to rename it? Is asinstancerename.exe just renaming SSAS, or is it attempting to change SQL Server and/or Windows too and that is why renames on clusters are not allowed?
Assuming I need to use this tool and I can, what login/password is it looking for? As I am a local administrator on the Windows box and an SSAS administrator, do I just pass in my Domain\Login + Password?
I'm probably overthinking some of this, but I am not familiar with this tool and the TechNet article leaves me with more questions than answers. I'm starting with the SQL 2014 Admin forum first, as this really more of an admin topic, but I will cross post to the SSAS forum if nobody seems to know.
Thanks to anyone who can shed some light on this!
Linda
November 21, 2017 at 8:00 am
linda-610451 - Wednesday, November 15, 2017 3:11 PMHello,Hoping somebody can help. We're migrating a very large vendor application to a 4-node AlwaysOn cluster. One node will be the reporting and analytics environment and will include AlwaysOn replicas of the prod OLTP databases. During the migration (this weekend) we'll be renaming the Windows server from "ServerHostnameNEW" to "ServerHostname." ServerHostname is the current environment hostname and this architectural design decision was made in consideration of the user base, so they would not have to repoint all their reporting and analytics tools.
I'm not sure what needs to happen with the SSAS server installed on "ServerHostnameNEW". I came across a Technet article stating you can rename an SSAS "instance" using asinstancerename.exe. I'm not sure if the Technet article refers to to the SQL Server instance name, or the windows hostname as the article keeps referring to this as an "instance" name change.
Additionally, Technet says asinstancerename.exe is not supported in a clustered environment. Frankly I'm a little confused. Are we talking all clustered environments or an active/passive clustered environment? There are multiple clustering options in SQL 2014? If renaming an SSAS install on an AlwaysOn node can not be accomplished with asinstancerename.exe, then how do I rename the SSAS installed there, or do I need to rename it? Is asinstancerename.exe just renaming SSAS, or is it attempting to change SQL Server and/or Windows too and that is why renames on clusters are not allowed?
Assuming I need to use this tool and I can, what login/password is it looking for? As I am a local administrator on the Windows box and an SSAS administrator, do I just pass in my Domain\Login + Password?
I'm probably overthinking some of this, but I am not familiar with this tool and the TechNet article leaves me with more questions than answers. I'm starting with the SQL 2014 Admin forum first, as this really more of an admin topic, but I will cross post to the SSAS forum if nobody seems to know.
Thanks to anyone who can shed some light on this!
Linda
asinstancerename.exe renames just the SSAS instance, not the SQL Server instance. Just the SSAS instance.
When it asks for the login and password, it's asking for the service account login and password, not your own.
There are different concepts in clustering - Windows Server Failover Cluster and Failover Cluster Instance. And there is more the Windows Server Failover Clusters than just active-passive. The stairways series on this site for AlwaysOn addresses some of this in relation to AlwaysOn:
Stairway to AlwaysOn
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply