You can write a very complex XMLport that exports and imports something like 12 tables. But you cannot do passwords. They are stored with one-way encryption.
Thanks for the reply.
Transferring passwords is important. What if the other database is a copy of the live database taken earlier? In this case, won't the encryption key is same in both databases?
"A bove maiore discit arare minor"-"From the old ox, the young one learns to plow."
Plan is to take a SQL backup and restore to another server. and keep the data as that date for some audit purpose.
Problem is users later change their passwords and forget the old ones. New users join. all in the live database.
But, for some urgent requirement, a user wanted to login, he don't remember the password or the user account doesn't exists.
So, if there is a way to transfer the users, their password and other permissions, this problem will be solved automatically (no need to call IT).
No need to see the password, just transfer them to the old db.
"A bove maiore discit arare minor"-"From the old ox, the young one learns to plow."
Seems like there is no generic solution. You could try to create a backup with Powershell and restore the backup in your secondary database. Then test if users still can login.
Answers
Transferring passwords is important. What if the other database is a copy of the live database taken earlier? In this case, won't the encryption key is same in both databases?
Problem is users later change their passwords and forget the old ones. New users join. all in the live database.
But, for some urgent requirement, a user wanted to login, he don't remember the password or the user account doesn't exists.
So, if there is a way to transfer the users, their password and other permissions, this problem will be solved automatically (no need to call IT).
No need to see the password, just transfer them to the old db.