Central Management Servers

Question

Central Management Servers

Steve Jones - SSC Editor

SSC Guru

Points: 734434
More actions
May 6, 2015 at 12:05 am

#74791

Comments posted to this topic are about the item Central Management Servers
May 7, 2015 at 4:23 am

This was removed by the editor as SPAM

Viewing 15 posts - 1 through 15 (of 15 total)

You must be logged in to reply to this topic. Login to reply

r0yster SSChasing Mays Points: 631 More actions · Answer 1

I CALL FOUL - the only correct answer to this should begin with 'It depends'. The CMS CAN be part of the server list by using the FQDN or IP address to list it, I have this configured in multiple places and it works fine. Also, since the db name in the question is the same on all 3 servers, you could run a single backup script but the backup disk location would need to be the same for all 3 servers <L:\BackupFolder\> and not to a network storage location. [<-- see, it depends] Using a network location would create problems as all 3 can't write to the same file simultaneously, nor would you want that. :crazy:

Ed Wagner SSC Guru Points: 287024 More actions · Answer 2

Nice question, but I guessed. I've heard good things about CMS, but never had the chance to really dig into them and play. Thanks.

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions

Raghavendra Mudugal SSChampion Points: 10658 More actions · Answer 3

Thank you for the question, Steve, nice one.

After reading this "Central Management Servers and subordinate servers can be registered by using only Windows Authentication. Servers in local server groups can be registered by using Windows Authentication or SQL Server Authentication." I guessed the local sever can also be registered in CMS and I selected 1 and I got red.

ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.

George Vobr SSCrazy Eights Points: 9914 More actions · Answer 4

I was wrong. Evidently I did not read this article carefully:

https://www.simple-talk.com/sql/backup-and-recovery/centralized-management-tips-for-managing-backups-on-multiple-servers/

SQLRNNR SSC Guru Points: 281334 More actions · Answer 5

r0yster (5/6/2015)
I CALL FOUL - the only correct answer to this should begin with 'It depends'. The CMS CAN be part of the server list by using the FQDN or IP address to list it, I have this configured in multiple places and it works fine. Also, since the db name in the question is the same on all 3 servers, you could run a single backup script but the backup disk location would need to be the same for all 3 servers <L:\BackupFolder\> and not to a network storage location. [<-- see, it depends] Using a network location would create problems as all 3 can't write to the same file simultaneously, nor would you want that. :crazy:

I agree. I register the CMS server within CMS as well.

In addition for the backup (and I grimace saying this), one can create backup devices on each instance and name the backup devices the same in each instance. The difference would be to have them pointing to different locations. Then a simple backup to device would be the same across all instances from a single script and it won't matter if it is local disk or if it is a network share.

Just another wrench for IT DEPENDS.:-D:-D:-D

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

RK Mandava SSCarpal Tunnel Points: 4153 More actions · Answer 6

SQLRNNR (5/6/2015)
r0yster (5/6/2015)
I CALL FOUL - the only correct answer to this should begin with 'It depends'. The CMS CAN be part of the server list by using the FQDN or IP address to list it, I have this configured in multiple places and it works fine. Also, since the db name in the question is the same on all 3 servers, you could run a single backup script but the backup disk location would need to be the same for all 3 servers <L:\BackupFolder\> and not to a network storage location. [<-- see, it depends] Using a network location would create problems as all 3 can't write to the same file simultaneously, nor would you want that. :crazy:
I agree. I register the CMS server within CMS as well.
In addition for the backup (and I grimace saying this), one can create backup devices on each instance and name the backup devices the same in each instance. The difference would be to have them pointing to different locations. Then a simple backup to device would be the same across all instances from a single script and it won't matter if it is local disk or if it is a network share.
Just another wrench for IT DEPENDS.:-D:-D:-D

+1

Steve Jones - SSC Editor SSC Guru Points: 734434 More actions · Answer 7

I'll reverse points on this one. I was trying to word as adding all the machines the same way. Adding some as SQLSales and some as 10.10.34.56 doesn't make sense. The FQDN is better, but you need to add everything that way, which isn't how I see most people do this.

pmadhavapeddi22 SSCertifiable Points: 5306 More actions · Answer 8

Truly, I have never done CMS to manager different servers. but to answer this QOD I have registered all the servers and run the backup script, script is executed on all the server except the main one but when I have added the first server using the IP , I could run the backup script on all the servers.

learnt something new today 🙂 It depends

Thanks for the question steve.

Hany Helmy SSChampion Points: 13921 More actions · Answer 9

SQLRNNR (5/6/2015)
r0yster (5/6/2015)
I CALL FOUL - the only correct answer to this should begin with 'It depends'. The CMS CAN be part of the server list by using the FQDN or IP address to list it, I have this configured in multiple places and it works fine. Also, since the db name in the question is the same on all 3 servers, you could run a single backup script but the backup disk location would need to be the same for all 3 servers <L:\BackupFolder\> and not to a network storage location. [<-- see, it depends] Using a network location would create problems as all 3 can't write to the same file simultaneously, nor would you want that. :crazy:
I agree. I register the CMS server within CMS as well.
In addition for the backup (and I grimace saying this), one can create backup devices on each instance and name the backup devices the same in each instance. The difference would be to have them pointing to different locations. Then a simple backup to device would be the same across all instances from a single script and it won't matter if it is local disk or if it is a network share.
Just another wrench for IT DEPENDS.:-D:-D:-D

Gr8 info, thanx.

Thanks & Best Regards,
Hany Helmy
SQL Server Database Consultant

Koen Verbeeck SSC Guru Points: 259085 More actions · Answer 10

Nice question, thanks.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

SADSAC SSCrazy Points: 2328 More actions · Answer 11

Never thought of using FQDN myself, so I learned something new from this discussion.

akljfhnlaflkj SSC Guru Points: 76202 More actions · Answer 12

Ed Wagner (5/6/2015)
Nice question, but I guessed. I've heard good things about CMS, but never had the chance to really dig into them and play. Thanks.

I guess too.

TomThomson SSC Guru Points: 104773 More actions · Answer 13

I know zilch about CMS so picked an answer at random (a wrong one, of course) to see what the correct answer was.

The answer as it stands makes me wonder how the thing is designed. For example, can I chain groups - ie can a CMS manage a group that contains another CMS that manages another group? If it can, do actions by the top CMS propagate down the chain? If they do, are loops in chains banned? If they aren't banned, what stops the loop?

Why does registering the CMS as a a member of a group it manages work if one uses a diferent designation - I can't see any good reason for banning including oneself (unless it's loop avoidance, which might or might not be a good reason). And I find it difficult to see why banning using one designation should be forbidden but using other designations for the same machine isn't. And of course here we have another incorrect statement in BOL (it's not the server that's banned from the group, it's a particular designation of the server).

I like Jason's comment on reaching distinct files and understand why he grimaces. I suspect he would grimace even more at the use of locally declared address mappings to override non-local DNS information as another means of achieving the same localisation of reference; I've used that in a non-database context and hated doing it. I think different mappings for backup device name are a bit cleaner than that. Obviously when I have had many customers running the same software and backing up to local (ie on same LAN) filestore the same backup device names have been used everywhere, but I never thought of it as a way of helping scripts from a centralised management system, just as names that were naturally and inherently local - no more interesting or controversial that having each server call all its main system disc C:, so Jason's suggested grimace-worthy use was new to me.

Tom