SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Should maintenance database be part of availability group ?


Should maintenance database be part of availability group ?

Author
Message
oskargunn
oskargunn
SSCommitted
SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)

Group: General Forum Members
Points: 1516 Visits: 362
Hi,

I have a custom maintenance and monitor database, which keeps history on database sizes, agent jobs, logon information and things like that.
Before AlwaysOn I didn't have any issues on how the setup should be, but ever since AO I am questioning whether to have the database inside the availability group or outside.
If it is inside an availability group, then I have a seperate step in my jobs that checks for primary. If I keep it outside the AO, then I have 2 seperate databases, which each keep their own split information, which I dont really want.
Is there anyone wondering about the same thing ?
Beatrix Kiddo
Beatrix Kiddo
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

Group: General Forum Members
Points: 27997 Visits: 7363
Does your maintenance & monitoring database do anything on the system databases? That might inform your decision.
Steve Jones
Steve Jones
SSC Guru
SSC Guru (603K reputation)SSC Guru (603K reputation)SSC Guru (603K reputation)SSC Guru (603K reputation)SSC Guru (603K reputation)SSC Guru (603K reputation)SSC Guru (603K reputation)SSC Guru (603K reputation)

Group: Administrators
Points: 603202 Visits: 21112
If this db is tightly bound to the user databases, maybe so. If not, it might warrant it's own AG. Either way, as Beatrix noted, if this depends on reading master/msdb/etc, you might need to rework things before putting this in an AG.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
oskargunn
oskargunn
SSCommitted
SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)

Group: General Forum Members
Points: 1516 Visits: 362
I do read msdb for the agent jobs, I keep a copy of jobs, to send alerts to nagios. The reason of keeping a copy of the jobs is the ability to acknowledge jobs that have failed.
I also read i guess the master database for info about database and datafile sizes. I keep track of it over time for statistical reasons.
And I get info about logins from SQLServer Error Log.
Steve Jones
Steve Jones
SSC Guru
SSC Guru (603K reputation)SSC Guru (603K reputation)SSC Guru (603K reputation)SSC Guru (603K reputation)SSC Guru (603K reputation)SSC Guru (603K reputation)SSC Guru (603K reputation)SSC Guru (603K reputation)

Group: Administrators
Points: 603202 Visits: 21112
The things I'd worry about with failover is strange behavior, or sending dup alerts. Maybe you read some data from master/msdb and load this into a table in your db, then process it?

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
DBA Pete
DBA Pete
SSC-Enthusiastic
SSC-Enthusiastic (186 reputation)SSC-Enthusiastic (186 reputation)SSC-Enthusiastic (186 reputation)SSC-Enthusiastic (186 reputation)SSC-Enthusiastic (186 reputation)SSC-Enthusiastic (186 reputation)SSC-Enthusiastic (186 reputation)SSC-Enthusiastic (186 reputation)

Group: General Forum Members
Points: 186 Visits: 2943

One solution is to use a single central maintenance and monitor database that is then added to an Availability Group for high availability.
The collected data just needs the full SQL Server instance name added, so it can be identified.

I have also seen a combined solution where the data is first stored locally and then copied into a central database.
When the central database cannot be reached, the maintenance and monitor information is not lost, just resent later.

Perhaps you can use this if it means less modification to your current maintenance and monitor system.
Use the local database for urgent alerts and the central database for less urgent reporting.






Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search