Timeline for Use sp_Blitz to gather information on all servers in a centralized server/database
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 6, 2017 at 19:40 | comment | added | Brent Ozar | Log shipping actually works fine if you use a view that unions across several databases. | |
| Feb 6, 2017 at 18:40 | history | edited | Kin Shah | CC BY-SA 3.0 |
added 317 characters in body
|
| Feb 6, 2017 at 18:38 | comment | added | Kin Shah | @BrentOzar Ok .. I understand that if many-to-one replication is implemented then its one possibility to aggregate info into central database. Logshipping just dont fit here since its at database level. OP want to have all info into a central database and so logshipping wont work in this situation. Personally, maintaining replication is another headache to maintain when the server(instance) count increases or changes. Good points though ! | |
| Feb 6, 2017 at 18:33 | comment | added | Brent Ozar | Sure, on each server, run sp_Blitz and write it to a table. Then, use options like replication or log shipping to copy that table to a central server. For example, when I was a DBA, I had a DBAtools database on every server. I wrote utility tables into that database, and then either used replication or log shipping (really full backup/restore) to bring them to a central DBA tools server. | |
| Feb 6, 2017 at 17:37 | comment | added | Kin Shah |
@BrentOzar Hi Brent .. sorry I did not get the part you can also use replication, log shipping, etc. Linked server is an option but replication, log shipping .. I dont understand. Thanks !
|
|
| Feb 6, 2017 at 17:34 | comment | added | Brent Ozar | Yep, in addition to doing sqlcmd, you can also use linked server queries, replication, log shipping, etc. | |
| Feb 6, 2017 at 17:28 | history | answered | Kin Shah | CC BY-SA 3.0 |