i seem to have an issue with security accounts in sql when cloning databases.
we are using snap manager for sql to create a snap shot and then clone the database to a different server. if a user is specified on the source server on the database (mapped user to that database) they can access the database without any issues (makes sense).
As soon as the clone happens at night it attaches to a different server. If i then look at the cloned database on the new server i can see the login account that is on the source server. if i try to login using sql management server (sql auth) it fails. If i re-map the account to the database then it works fine until the next night which means i have to reset the permissions every morning. The only way around this is to assign to the account sys admin on the sql server whhich is not very secure at all.
any suggestions on a work around or if i am missing anything?