Use a server alias in data source of on-premise report server

[Anonymous]

We us an alias for our sql server, implemented via the DNS. 

But when using the alias in a data-source setting of the report server it doesn't work, we need to use the absolute address.

is it possible to fix this or a native report server way of not handling aliases

[Anonymous]

I am sorry probably i have not been clear enough.

It is not the alias of the reportserver but the alias of thesource system in the datasource.

we have a sql server databaseserver and this has been given an alias.

Once developing reports in excel and powerbi this alias works well. Once publishing these reports on a centralized location like report server the alias used in the datasource does not work anymore and we need an absolute reference.

[Anonymous]

Thank you very much we will implement this and once it works i will accept it as a solution

[Anonymous]

Hi @Anonymous ,

To use a SAN, the TLS/SSL certificate must be registered on the server, signed, and have the private key. You cannot use a self-signed certificate.

URLs in Reporting Services and Power BI Report Server can be configured to use a TLS/SSL certificate. A certificate normally has just a subject name, which allows only one URL for a Transport Layer Security (TLS), previously known as Secure Sockets Layer (SSL), session. The SAN is an additional field in the certificate that allows a TLS service to listen for many URLs, and to share the TLS port with other applications. For example, a SAN could look something like www.myreports.com.

For more you may refer to Configure Reporting Services to use a Subject Alternative Name (SAN) - SQL Server Reporting Services (SSRS) | Microsoft Learn

Best Regards,
Community Support Team _ Caitlyn

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.