Skip to main content

Rename an Analysis Services Instance

This is just a short post for Friday. I have been working a fair amount with SSAS and the rest of the BI stack and recently  I was asked to install a default instance of SSAS on server that already had a named instance installed. I didn’t think this would take me a long time I had a quick look at Configuration Manager saw the named SSAS instance mounted up the ISO and off I went.

Click click click click done. Oh an Error…”The instance ID needs to be unique please ”  on further investigation it seemed that the existing named instance had the default instance ID. How could that be I thought?

It turns out that the current named instance was initially installed as the default instance then got renamed. SSAS instances are far more easily renamed than  Database Engine instances. The recommended way to change a database engine default instance to a named instance is to uninstall and re-install the server. Fortunately with SSAS the process is much more straight forward.

SSAS actually ships with an instance rename tool, this article on the Microsoft  site talks you through how to use it

My rename tool can be found her

C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE

The tool is called ASInstanceRename.exe

Fire it up and you get a screen that looks like this


Select an instance to rename from the drop-down list and specify the new name for the instance. In this case I’m renaming my default instance and making it a named instance imaginatively called NewInstance. You click on OK and the instance gets renamed and I get a named instance of SSAS

Now I’d have to connect to the SSAS instance using ServerName\InstanceName

If you want to make a named instance the default instance, then you leave the new instance name field  blank. This process will fail if you already have a default instance.


Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…