• Depending on the nature of the change/move, you may want to set service start to Manual for all SQL Service.
• Once things or up and running properly, return service start to its original setting.

• If all administrator accounts are domain accounts or groups, temporarily enable the 'sa' account with a strong password.
• Once the domain-based accounts are setup in the new domain, 'sa' can be disabled again.

• For each SQL-Server-related Windows service, change the service to use a LOCAL windows account or one of the built-in accounts.
• Grant the necessary privileges to the service new domain accounts. When special permissions are not needed, the SQL Service Configuration Manager can be used to change the service account.

• OLD firewall openings that are no longer used will need to be closed, NEW firewall openings may need to be created for SQL Server, OLAP services, SSRS between servers and clients.

• Verify DNS has correctly updated.
• Clients and services that reference by DNS name may need to be restarted AND/OR their host systems may need their DNS cache flushed. For windows workstations, this can be done with "ipconfig/flushdns"

Service Principle Names (SPNs). Some standalone (and all clustered) instances use SPNs. (Need to be checked with windows team whether they will do it or not)

• The OLD SPN must be dropped and a NEW SPN must be created. Although it's not recommended to use a SQL Server service account to manage (its own) SPNs, if this is the case, the NEW domain service account will need to be granted Write Service Principal Name" privilege

• Data Source Names (DSNs), connection strings, config files, Oracle TNS names for connections - will need to be updated and applications and services may need to be restarted.

• If the machine name is also changing, SQL Server's internal machine name entry may need to be updated.

sp_dropserver <old_name>;

GO

sp_addserver <new_name>, local;

GO

Restart the SQL server after renaming it and use below query to find the new name of the server.

       Select @@SERVERNAME

• Ensure all replicas are up-to-date
• Re-configure merge replication

1. Stop all services of SQL server not to automatically start
2. Create new service accounts and update it for the SQL services using configuration Manager.
3. Create a Logins with new domain account: Take a backup of existing Logins which are created from Windows and create a new one with new domain account.
4. Change the users with new Logins: Take backup of all the above Logins and update the login name and user name and create new users.
5. Change memory location for the new User: Enable Lock Pages in Memory in Group Policy Editor:

ü  On the Start menu, click Run. In the Open box, type gpedit.msc

ü  On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.

ü  Expand Security Settings, and then expand Local Policies.

ü  Select the User Rights Assignment folder.

ü  The policies will be displayed in the details pane.

ü  In the pane, double-click Lock pages in memory.

ü  In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.

ü  In the Select Users, Service Accounts, or Groups dialog box, add an account with privileges to run sqlservr.exe.

ü  Log out and then log back in for this change to take effect.

1)      And finally start the services.

     To update the password, do the following:

ü  On the Start menu, point to Control Panel, point to Administrator Tools, and click Services.

ü  Right-click SQL Server Reporting Services, select Properties.

ü  Click Log On, and type the new password.

ü  After you update the password, start the Reporting Services Configuration tool and update the password in the Service Account page. This additional step is necessary to update the account information that is stored internally by the report server.

ü  Need to change the Role assignments to new user accounts.