Quantcast
Channel: SQL Server Manageability forum
Viewing all articles
Browse latest Browse all 1519

Using Failover Server in Always on For Reporting ....user and login issues

$
0
0

Here I go again….
Let me start, as usual by thanking everyone who has been kind enough to reply to previous posts.
And if you have, or even just read them then you will know I tend to be long winded so I will make an effort to get to the point.

What I have:

Server 1 backups up a database every 12 hours.
Server 2 restores that backup from Server 1.
Server 2 is used for reporting only and is at least 12 hours behind.
When it is restored I have to go to the restored database > Security > Users and delete the user ‘Reporter’.
Then go to Instance Security > Logins  and remap user ‘Reporter’ set permissions, etc.

This is where you all say “Always On Availability Groups”!

Well, yea. And that’s where I am.
I have set it up, Server 1 Server 2, same database on both, etc.
The user ‘Reporter’ is on Server 1 (where it pretty much started) and all works well.
But the minute I go into Server to and try and do ANYTHING with user Reporter in either the database level or Instance level I get nowhere QUICK..
When it says “READ ONLY” it means READ ONLY on everything.
I really need to get this one user to be able to hit Server 2 for reporting.
Any ideas and/or quick fixes?

P.S. when I set up group I made it secondary readable


R. Brown


Viewing all articles
Browse latest Browse all 1519

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>