In our previous webinar entitled “Leveling up your Oracle and SQL Server Farm Management,”, we discussed ways to distribute server load, automate DBA tasks, and utilize internal communication. For this blog, we will tackle the essentials of multi-domain on a deeper level.
You can click on the webinar link above for IT managers and database administrators who are unaware of dbWatch domains. The webinar captures ways to distribute load for monitoring and management tools ideal for any database management system. More specifically, it targets:
- - SQL Server Management
- - Oracle Management
- - SQL Server database monitoring
- - Oracle database monitoring
Overview of dbWatch Domain in Practical Application
To begin with, our setup will comprise of two servers. The details are listed below:
In this setup, each dbWatch domain will have database instances attached to them. In addition, we will monitor the remote server – REY using DBWLAP0091. The structure is as follows:
Structure of connection between two dbWatch domains and their registered instances
As you can see, DBWLAP0091 directly connects to six database instances. It has a mix of different platforms such as Postgres, SQL Server, Oracle, and MySQL. On the other hand, REY has nine database instances with the same platform variety. Essentially, we are doing SQL Server database monitoring and Oracle database monitoring at the same time.
Database instances found in DBWLAP0091 are only grouped for Production, while REY spreads across Development, Test, and Production. In completing the setup, DBWLAP0091 connects to server REY with dbWatch user credentials for that domain.
When translated to dbWatch’s monitoring overview, you can see the difference between REY and DPLAP0091’s monitoring overview.
Monitoring Overview for "REY"
Monitoring Overview for DPLAP0091
Advantages of a centralized overview
In SQL Server database monitoring and Oracle database monitoring, a centralized view is essential to a monitoring tool. This added convenience makes it easier for the end-user to perform their DBA tasks efficiently.
With one dbWatch console acting as the central hub, it becomes easier to monitor, manage and report for your registered instance. Even with a hard limit of ten licenses for server REY and six instances for server DBLAP0091, I can still monitor a total of fifteen instances.
For example, you wanted to see an overview of all registered instances under one view. All registered instances for both domains are seen in the Resource Overview found in the Database Farm Module.
Database Farm: Instance overview of all registered instances.
The farm view sees database instances as a single collective network. This unified network works well with Oracle database monitoring and Microsoft SQL Server database monitoring. Think of it like this: your database farm is monitoring another database farm. Pretty convenient!
Next, Oracle Management and SQL Server management become easier under this setup. For example, you wanted to see the sessions of an SQL database instance named "Gorsh". Server REY holds Gorsh as one of its registered instances and we are currently accessing the database instance through the same server - REY.
Sessions found in database instance "Gorsh"
Notice how Gorsh does not display DBWLAP0091 as any of the sessions for Gorsh. It implies that the connection between DBWLAP0091 and server REY mediates all configurations and deployment done in Gorsh. Coincidentally, when you also apply changes in configuration and fixes, DBWLAP0091 will apply those fixes as server REY and not as DBWLAP0091.
Then, we have the Report Module to specify which dbWatch domain you want to generate a report. The process is the same as a single dbWatch Server.
Generating a report
Finally, you have the option to monitor your dbWatch domains. Go to Views and tick the Internal View selection.
Monitoring your dbWatch domains
In this overview, you can monitor all your dbWatch status. It has the necessary components such as licenses, server disk usage, and memory and CPU statistics.
How to Add or Change dbWatch Domains?
You can add an existing dbWatch server by going to “Add dbWatch Server” and inputting the host IP and the port number of that dbWatch server. By default, all dbWatch Control Center servers are running in port number 7100.
Afterward, input that dbWatch Server’s username and password. Then, click “Test” on the right-most pane and wait to see a green checkmark. This checkmark indicates that the current dbWatch server can connect to that existing dbWatch Server. Otherwise, either your dbWatch server cannot be located, or there are problems with the credentials.
Additionally, always check if the column of “Connect” has a checkmark. That means dbWatch Control Center will also connect to that existing dbWatch Server.
dbWatch Control Center running in DPLAP0091 with a connection for server REY and removed connection for server DPLAP0091
Take the above image, for example. The ticked connection is for REY but not for DPLAP0091. This action will only display all the database instances under REY.
In summary, we discussed the differences and advantages of using a multi-domain dbWatch Server. This setup has more centralized and distributed means of Oracle database monitoring and SQL Server database monitoring. In addition, you can perform Oracle management and SQL Server management using this setup.
You can try Control Center today. Use this link to download a version of dbWatch that can monitor up to 5 instances for six months for free: dbWatch Control Center free license
If you have any questions or you would like to know more on how dbWatch can assist you in your current enterprise database monitoring and management situation, feel free to contact me directly: firstname.lastname@example.org
#DBA #DatabaseManagement #databasemonitoring #sqlserver #oracle #mysql #databasemonitor #microsoft sql server
About the Author:
Rey Lawrence Torrecampo is a Pre-sales Engineer for dbWatch and a full-time Database Administrator. He has extensive knowledge in Postgres and MSSQL database management systems, with SQL as his most proficient language.