What is the impact of restoring an enterprise geodatabase in SQL Server on ArcGIS software?

What is the best practice to restore the SQL Server Database (EGDB)? Do we need to always overwrite the existing database with the same name?

In general, the best practice is to restore an enterprise geodatabase in SQL Server using the same name.  This approach is recommended because, in geodatabase versions 10.9.x, the geodatabase (GDB) system tables rely on the database name. Restoring with a different name may lead to various issues.

Is there any possibility to restore the SQL Server Database (EGDB) with a different name? I saw a reference indicating this is supported only in ArcGIS Pro 3.x versions.

Yes, it is possible to restore a SQL Server Database (EGDB) with a different name starting with geodatabase version 11.x. However, to enable this capability, the geodatabase must first be upgraded using at least ArcGIS Pro version 3.x. This upgrade modifies the geodatabase structure to support restoration under a different name.

Considerations when restoring with a different name:

• Changing the name of a SQL Server database that contains an enterprise geodatabase should not be a frequent practice, as it has impacts referenced map services similar to migrating the SQL Server instance to a different server
• The referenced map services utilize the instance name (database name and server name) in the database connection. Changing the database name will cause the referenced data connection to break.
• For ArcGIS Pro, you must repair the database source in map documents, projects, and layers.
• For ArcGIS Server, web services must be republished.