Solved! Go to Solution.
1. Take a complete backup of the Geodatabase (Through SQL Server).
2. Install SQL Server 2008 R2 on the new machine. (If you have SQL Server 2008 R2 installed on new machine, then skip step 2 and Restore the database).
3. Restore the database. (The one which Ii had mentioned in step 1).
4. Re-synch SQL Server logins
I would suggest you to try Step 3 and Step 4 in the new machine. I understand that SQL Server is installed in the new machine. You can go ahead and restore the database and Re-synch SQL Server logins.
I am connected to the database in catalog as the sysadmin user. On top of Sysadmin, I've ensured that the default schema is identical to the name of the user, just as you've stated to do. Despite this, when I copy data from one gdb and into my target, the schema is still dbo and not the default schema I've registered with the user I'm connected with.
A user who has been granted the 'sysadmin' server role, will always use DBO schema.
If you want the data owner to be the username:
Remove SYSADMIN > match the Username and Default Schema in User Mapping > grant the necessary permissions needed for creating\loading data.
Thank you for the quick reply.
Using a separate sysadmin account, I removed the sysadmin role from the user I wish to use. Continued to navigate to instance>security>user>user mapping -- edit the user and default schema fields on the database I'm working on > error: Rename fialed for User 'dbo' .... Cannot alter the user dbo