Here is the step 9 we will be able to notice that how a user without login gets access to some of the data/object which we gave permission.

What I am going to prove with this example? Well there can be different rights with different account. Once the login is authenticated it makes sense for impersonating a user with only necessary permissions to be used for further operation. Again this is very basic and fundamental example. There are lots of more points to be discussed as we go in future posts. Just do not take this blog post as a template and implement everything as it is.

Database Mirroring is a disaster recovery solution and to add more its a database solution and not a server solution.

Since it is a database solution all users inside a database already mirrored but logins are maintained at server level(master db to be specific) and logins are not mirrored. Same case with Log Shipping also.

To address this issue, I created a daily evening SQL job that sync windows logins between principal and mirroring server. You can also do this real time by using DDL Triggers for “Create Login” Event.

Pinal Dave is a technology enthusiast and an independent consultant. He has authored 11 SQL Server database books, 21 Pluralsight courses and have written over 3800 articles on the database technology on his blog at a http://blog.sqlauthority.com. Along with 14+ years of hands on experience he holds a Masters of Science degree and a number of database certifications. For any SQL Server Performance Tuning Issue send email at pinal @ sqlauthority.com .

Nupur Dave is a social media enthusiast and and an independent consultant.