Rename an Analysis Services Instance
Applies To: SQL Server 2016
You can rename an existing instance of Microsoft Analysis Services by using the Rename Instance tool, installed with Management Studio (Web install).
The Analysis Services Instance Rename tool does not modify the program folder that was created for the original instance. Do not modify the program folder name to match the instance you are renaming. Changing a program folder name can prevent Setup from repairing or uninstalling the installation.
Launch the Instance Rename tool, asinstancerename.exe, from C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn\ManagementStudio.
In the Rename Instance dialog box, in the Instance to rename list, select the instance that you want to rename.
In the New instance name box, enter the new name for the instance.
Verify that the user name and password are correct, and then click Rename.
The Analysis Services instance will be stopped and restarted as part of the name change.
To resume access to databases that are running on the renamed instance, you will need to manually update the data connections in Excel or other client applications. Also check any predefined connections, such as Reporting Services shared data sources, Excel ODC files, or BI Semantic Model connection files that might reference the instance you just renamed. For more information, see Connect to Analysis Services.
Update PowerShell scripts or AMO scripts that you routinely use to backup, synchronize, or process databases.
Update project properties for Analysis Services projects that you work with in SQL Server Data Tools. For tabular mode server instances, be sure to update the Workspace Server property on the model.bim file, as well as the Server property on the project.
Depending on how you specified the service account, you might need to update database logins or file permissions that grant data access rights to the service (for example, if you use the service account to process data or access linked objects on another server).
Updating a database login or file permissions will be necessary if you used a virtual account to provision the service. Virtual accounts are based on the instance name, so if you rename the instance, the virtual account is also updated at the same time. This means that any previous logins or permissions that you created for the previous instance are no longer valid.
The following example provides an illustration. Suppose you installed a tabular mode server as an instance named “Tabular” using the default virtual account, resulting in the following configuration:
Instance name = <server>\TABULAR
Service name = MSOLAP$TABULAR
Virtual account = NT Service\ MSOLAP$TABULAR
Now suppose you rename the instance to “TAB2”. As a result of the name change, your configuration would now look like the following:
Instance name = <server>\TAB2
Service name = MSOLAP$TAB2
Virtual account = NT Service\ MSOLAP$TAB2
As you can see, database and file permissions that were previously granted to “NT Service\ MSOLAP$TABULAR” are no longer valid. To ensure that tasks and operations performed by the service run as before, you would now need to grant new database and file permissions to “NT Service\ MSOLAP$TAB2”.