• Hi everybody ,

    My answer was Yes, because I have read in my local MSDN this :

    Moving the Resource Database

    In SQL Server 2008, the default location of the Resource database is <drive>:\Program Files\Microsoft SQL Server\MSSQL10.<instance_name>\Binn\. The database can be moved; however, we recommend against moving it for two reasons:

    Applying SQL Server service packs and hotfixes restores the database to the \Binn location.

    Moving the Resource database in a failover cluster environment to a nonclustered location will cause failover cluster failure.

    To move the Resource database, follow these steps.

    Stop the instance of SQL Server if it is started.

    Start the instance of SQL Server in master-only recovery mode by entering one of the following commands at the command prompt. The parameters specified in these commands are case sensitive. The commands fail when the parameters are not specified as shown.

    For the default (MSSQLSERVER) instance, run the following command.

    Copy Code

    NET START MSSQLSERVER /f /T3608

    For a named instance, run the following command.

    Copy Code

    NET START MSSQL$instancename /f /T3608

    For more information, see How to: Start an Instance of SQL Server (net Commands).

    Using sqlcmd commands or SQL Server Management Studio, run the following statements. Change the FILENAME path to match the new location of the data file. Do not change the name of the database or the file names.

    Copy Code

    ALTER DATABASE mssqlsystemresource

    MODIFY FILE (NAME=data, FILENAME= 'new_path_of_master\mssqlsystemresource.mdf');

    GO

    ALTER DATABASE mssqlsystemresource

    MODIFY FILE (NAME=log, FILENAME= 'new_path_of_master\mssqlsystemresource.ldf');

    GO

    Move the mssqlsystemresource.mdf and mssqlsystemresource.ldf files to the new location.

    Set the Resource database to read-only by running the following statement.

    Copy Code

    ALTER DATABASE mssqlsystemresource SET READ_ONLY;

    Exit the sqlcmd utility or SQL Server Management Studio.

    Stop the instance of SQL Server.

    Restart the instance of SQL Server.

    Is that wrong ?

    Thanks in advance.