Is “Readable Secondary” is default setting (No), is that still an instance? (SQL12)

a) if the setting “Readable Secondary”  is set to No, is the secondary still considered an instance?
LVL 5
25112Asked:
Who is Participating?
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
1) I don't master contained databases because I never used them but by the articles I read I can't see any cons.
2) Maintenance Plan from SSMS are better than nothing and they are there for non-DBA users can use them easily but if true DBA's hate them (I do) since they aren't flexible at all and don't let you make changes on them and that's why DBA's have their own scripts so they can control all maintenance tasks. A big number of DBA's use the one from Ola's and some of them changed that script for work as they want giving them much more flexibility.
0
 
25112Author Commented:
In that case,
1)can you or should you create a separate list of logins with the same SID's as the primary instance?
2)Can you create Maintenance plan on secondary (or should you as a standard)?. just as in the primary?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
a) Yes. Usually used for DR instance.
1) Yes. Needed when used for DR solution.
2) You can create in Secondary but apart from being a little bit more complex, when failover to Secondary Replica means that will be the Primary so you need to remember to failback when Primary Node is up again.
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

 
25112Author Commented:
>>1) Yes. Needed when used for DR solution.
OK.. what are the considerations to remember or keep as reference when doing this? (like keeping SID alike in both instance etc).. what else?

>>2) You can create in Secondary but
so, you would suggest Maintenance plan on secondary is not a prime need or focal point, as long as you shift the nodes back to place, right?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
1) For that you need to following the actual Microsoft procedure that is in this MSDN article.
2) What I meant is that what is a Secondary today can be Primary tomorrow so I wouldn't lose much time with this and will configure the jobs on all servers in the AlwaysOn availability group so they won't be impacted by any failover.
Ola Hallegren's have very good scripts that works well with AG and you don't need to worry about them after. Just download the scripts and run on the AG.
0
 
25112Author Commented:
thanks.,

1)I was reading more, and do you see any reason to consider
https://msdn.microsoft.com/en-us/library/ff929071%28v=sql.110%29.aspx
over
the link you gave.
(in relation to handling the syncing login issue)

2)can you suggest exact link in Ola Hallegren for maintenance plan scripts to keep in both servers (primary & secondary)
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
1) Contained databases are different thing. I don't even know why are you considering them.
2) It's there exactly in the link I've sent you. The script is MaintenanceSolution.sql and you just need to run it in all instances that you have and it will do everything for you.
0
 
25112Author Commented:
Vitor,
1)
I see what you are saying.. contained databases are not directly related, but are they indirectly? do you see any cons in using them for keeping logins in sync?
2)
thanks for pointing to the .sql. I am going to try it on a test box. personally what difference or benefits do you see in using sql scripts vs the native maintenance plan that comes with SSMS?
0
 
25112Author Commented:
helped.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.