DBMSys Platform

DBMSys platform was designed to capture, process, report, and guide automation decisions based on metadata from multiple platform environments. DBMSys uses an agentless central engine to collect varying kinds of data, both structured and unstructured, on nearly any infrastructure. The platforms and collection types covered by DBMSys expand on a regular basis.

Examples of what DBMSys captures include:

• Operating System information
• Database-instance/Web Servers/Exchange/Active Directory level specific information
• Performance data
• Activity logs

Note: DBMSYS does not access the content of any user table. All information collected by the application is going to be available on the application’s database for review and auditing by the customer.

With the database server and hardware profile, operating system information, and metadata in hand, our solution architects can determine the risk to the business based on product supportability and new-feature adoption. Our first consideration is to look for databases and servers running on versions of the operating system or database server that are out of support or on extended support. These servers represent a business risk that you need to address. We also look for software running on aging servers.

Technology has advanced over the years with faster CPUs, greater memory capacity, and new storage technologies like flash-based solid-state drives. These servers are great candidates for consolidation and virtualization (Hyper-V and VMWare ESXi) on a modern host server or for moving to the cloud. The analysis also looks at database usage to determine if a server is a candidate for decommissioning; scaling down in a consolidated platform due to its lack of use.

DBMSys can also collect data from Oracle database servers to assess the possibility of migrating from Oracle to another database platform like SQL Server.

DMBSys includes additional algorithms to compute the optimum configuration for moving the application databases to either Azure, AWS, or Google Cloud Platform (GCP) environments. By analyzing the workload usage data, DBMSys can recommend specific Azure, AWS, or GCP VM sizes that match up with the usage data to determine if a database instance should be on a single VM or have multiple instances on a single VM. DBMSys can also compute the estimated monthly costs using the latest billing information from Azure, AWS, or GCP.

Building a financial model without current environmental metadata can be a daunting task. DBMSys helps develop a model by showing a breakdown of what the current state is and comparing the possible solutions that have been predetermined from the client’s guidance.

Some of the possible scenarios that can be compared include:

• Current state—do nothing
• Move existing servers to Azure/AWS/GCP virtual machines with or without consolidation
• Perform Consolidation among existing on-premises servers
• Virtualize existing on-premises servers to Hyper-V/VMware

We seek to empower our customers with their own data to help make the best business decisions regarding their future state architecture. It’s important that our customers have a full understanding of the overall cost model with input from DBMSys and our engineers.

With DBMSys, we are able to provide health monitoring, upgrading, and patching all through one platform. DBMSys can also be used for many other reporting and environmental tasks that require a real-time monitoring system to help guide the decision-making process.

We deploy DBMSys for long-term engagements to assist with health monitoring, system status, and other business-rule requirements. DBMSys displays metadata on a single health dashboard. DBMSys takes real-time alerts, events, and metadata and uses predefined business rules to create targeted alerts and actions. This gives your infrastructure and database teams greater control over the environment.