AXISHK
asked on
Restore SQL Database
Can we backup a SQL2008R2 standard database and restore it into SQL 2008R2 Enterprise ? Is there anything that I need to be aware of ?
Tks
Tks
Wilder_Admin
This should work with a sql dump because here you really dump data there are no informations out of which database systems they come from.
Restoring to a higher edition of the same version will work fine.
You may need to run a "fix logins" script if your database has an domain users, but you would have to do that anyway if moving to another server, so isn't unique to your scenario.
You may need to run a "fix logins" script if your database has an domain users, but you would have to do that anyway if moving to another server, so isn't unique to your scenario.
ASKER
"fix logins" ... I am not aware of this issue. Can you give me more information about this, Tks
ASKER
EXEC sp_change_users_login 'Report', the following are listed.
UserName UserSID
bakerpreport 0x9DF2F5CD331FF14AB4B345B3
erpreport3 0x0F42C6E03696B649BE9D8E20
SalesReportingAX2009 0xBC60008F737DE748975E795E
puradmin 0xE26A5AC1075F7B42A20D641C
reportuser 0x9E9DCE427AD01543A5E81A90
Afterwards, I issue "EXEC sp_change_users_login 'Auto_Fix', 'bakerpreport' ". The following message is logged, Tks
"Msg 15600, Level 15, State 1, Procedure sp_change_users_login, Line 214
An invalid parameter or option was specified for procedure 'sys.sp_change_users_login
UserName UserSID
bakerpreport 0x9DF2F5CD331FF14AB4B345B3
erpreport3 0x0F42C6E03696B649BE9D8E20
SalesReportingAX2009 0xBC60008F737DE748975E795E
puradmin 0xE26A5AC1075F7B42A20D641C
reportuser 0x9E9DCE427AD01543A5E81A90
Afterwards, I issue "EXEC sp_change_users_login 'Auto_Fix', 'bakerpreport' ". The following message is logged, Tks
"Msg 15600, Level 15, State 1, Procedure sp_change_users_login, Line 214
An invalid parameter or option was specified for procedure 'sys.sp_change_users_login
If you're using "Auto_Fix" then you need to supply a password. Auto_Fix will create a matching login if one doesn't already exist - which, depending on your security policy, you may or may not want it doing.
You might be better using "Update_One" option instead to ensure you are only mapping existing logins.
You might be better using "Update_One" option instead to ensure you are only mapping existing logins.
ASKER
so, should I issue,
use database_name
go
EXEC sp_change_users_login 'Update_One', 'bakerpreport', 'bakerpreport'
go
use database_name
go
EXEC sp_change_users_login 'Update_One', 'bakerpreport', 'bakerpreport'
go
I would.
ASKER
It returns with the message below. However, EXEC sp_change_users_login 'Report' show the user "bakerpreport". However, I can't see the name under MS SQL Server Management Studio -> Security -> Logins. What does it mean ? Tks
Msg 15291, Level 16, State 1, Procedure sp_change_users_login, Line 137
Terminating this procedure. The Login name 'bakerpreport' is absent or invalid.
Msg 15291, Level 16, State 1, Procedure sp_change_users_login, Line 137
Terminating this procedure. The Login name 'bakerpreport' is absent or invalid.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Tks