Hi All, We are migrating from one SQL server to another and we have an RS setup that has many individual data sources pointing to the original server. Question is, is there a way we can update the data sources (using TSQL against datasource table in ReportServer db..or something like that) with the new server name, without having to manually update each one in Report Manager? Problem is, there may be hundreds (dont ask!) pointing to the old server name. Thanks in advance!

Hi dnaman, To achieve your purpose, a solution is using alias. An alias is an alternate name that can be used to make a connection. The alias encapsulates the required elements of a connection string, and exposes them with a name chosen by the user. Please follow these steps to create an alias: 1. On the server which has Reporting Services installation, from the Start menu, click All Programs, select Microsoft SQL Server 2008/Configuration Tools/SQL Server Configuration Manager. 2. In SQL Server Configuration Manager, expand to SQL Native Client 10.0 Configuration/Aliases, right click New Alias. 3.In Alias - New window, input the original server name to Alias Name, the pipe name/VIA parameters/port number/ of new server to Pipe Name/VIA Parameters/Port No, the protocol of new server to Protocol, the IP/server name of new server to Server, then click OK. 4. Check every data source and make sure whether they work fine. If there is anything unclear, feel free to ask. Thanks, Albert Ye

Hi dnaman, To achieve your purpose, a solution is using alias. An alias is an alternate name that can be used to make a connection. The alias encapsulates the required elements of a connection string, and exposes them with a name chosen by the user. Please follow these steps to create an alias: 1. On the server which has Reporting Services installation, from the Start menu, click All Programs, select Microsoft SQL Server 2008/Configuration Tools/SQL Server Configuration Manager. 2. In SQL Server Configuration Manager, expand to SQL Native Client 10.0 Configuration/Aliases, right click New Alias. 3.In Alias - New window, input the original server name to Alias Name, the pipe name/VIA parameters/port number/ of new server to Pipe Name/VIA Parameters/Port No, the protocol of new server to Protocol, the IP/server name of new server to Server, then click OK. 4. Check every data source and make sure whether they work fine. If there is anything unclear, feel free to ask. Thanks, Albert Ye

Albert, How can one achieve this same functionality without a RS front end and an SQL alias? If we migrate a database with a rather large user base where we allow direct connectivity for ad-hoc queries how do we provide connectivity to the previous server name without requiring that every user update their connection settings? Obviously I understand that this is probably a less than ideal practice but it would be short term. I considered using the same modifications to Lanmanger that are used by a DFS consolidation where the server would respond to multiple names via Netbios/WINS. Does this method work and if not is there another way without requiring static DNS records?

Albert, How can one achieve this same functionality without a RS front end and an SQL alias? If we migrate a database with a rather large user base where we allow direct connectivity for ad-hoc queries how do we provide connectivity to the previous server name without requiring that every user update their connection settings? Obviously I understand that this is probably a less than ideal practice but it would be short term. I considered using the same modifications to Lanmanger that are used by a DFS consolidation where the server would respond to multiple names via Netbios/WINS. Does this method work and if not is there another way without requiring static DNS records?

Albert, How can one achieve this same functionality without a RS front end and an SQL alias? If we migrate a database with a rather large user base where we allow direct connectivity for ad-hoc queries how do we provide connectivity to the previous server name without requiring that every user update their connection settings? Obviously I understand that this is probably a less than ideal practice but it would be short term. I considered using the same modifications to Lanmanger that are used by a DFS consolidation where the server would respond to multiple names via Netbios/WINS. Does this method work and if not is there another way without requiring static DNS records?