Databases Reference
In-Depth Information
Figure 2-16.
Azure monitoring implementation
The monitoring provider has also built a portal on which customers can monitor their SLAs. Customer B, for
example, can now use the portal to monitor both its CRM and ERP application database SLAs. The customer can
prepare reports and make them available to the ERP and CRM vendors for review online, with complete drilldown
access to the statements from the same portal.
In this implementation, additional benefits include the following:
•
Improved sharing.
Sharing information with vendors becomes much easier because
drilldown access to issues is provided through a cloud-enabled portal.
•
Local storage optional.
With the improved solution, customers may decide to implement
the cloud storage only if they're short staffed to handle the necessary internal database-
management activities.
•
External monitoring.
Customers A and B also have the ability to use the monitoring provider
to monitor their ERP products proactively and remotely with specific escalation procedures
when the SLAs aren't met. The monitoring provider can, for example, manage performance
issues directly with the ERP provider.
Other Considerations
This chapter has introduced many important design factors to help you design a solution that uses SQL Database. Are
few more concepts are worth a glance, such as blob data stores, edge data caching, and data encryption.
