Name of University

Discussion Forum

(Managing Virtual Environments)

Name

Date
 Standard Protocol versus Proprietary Protocol

Proprietary protocols provide an excellent opportunity for vendor "lock-in." Your

solution will still need the involvement of the vendor. Similarly, this was true of early

information technology solutions. Proprietary protocols may be used to enhance a product's

or solution's functionality. The industry has grown to the point that the emphasis is now on

open standardized protocols that enable the interconnection of disparate systems - in other

words, system interoperability. It is strongly advised to utilize standard protocol rather than

proprietary protocol, since standard protocol may be used into a broad variety of decisions of

any other firm.

While proprietary protocols are company-specific, this implies that your device

operates on a proprietary protocol that is used only by that business, making it difficult to

integrate devices from other companies into your system. In comparison to conventional

protocols, proprietary protocols are more secure. Standard protocols make their data

accessible to anybody, making them susceptible to hackers who may simply discover how to

access and manipulate the network. Whereas with proprietary protocols, cybercriminals or

hackers will require additional resources and time to comprehend how the protocol is

constructed and what its weaknesses are. (Decusatis et al, 2012)

Even while proprietary protocols are more secure than the standard protocols, they are

still not the best solution since they are tied to a particular organization, whereas standard

protocols are not. Whereas standard protocol gives you more freedom since it is supported by

a wide number of devices, making it easy to connect them. Additionally, you will prevent

vendor lock-in by having the option of choose from a broader range of device manufacturers

that provide devices that communicate using the same language. This is why standard

protocols are more prevalent than proprietary protocols.

 Baselines

Each system is distinct from the others. We may assert that, despite the fact that

databases might be identical across systems installed by the same manufacturer, each

organization is distinct. Users are another variable in the equation, in addition to business

differences. By combining these, we may arrive at a general equation that will generally

result in a variable value. (Casazza et al, 2006)

Apart from following standard performance optimization standards, it is vital to understand

the particular effect on the database server during typical operations. This enables the

management of known performance fluctuations and, more crucially, the monitoring of

unpredictably variable performance variations. Without baselines, we can modify database

performance, but not to the level that the unique business and user implications need. Having

a performance baseline is critical for determining if an increase in resources use is an issue.

 The primary goal of establishing a baseline and benchmark is to determine clearly

what constitutes normal and abnormal behaviour for your SQL Server. In the absence

of this information, you are forced to depend on broad generalizations and hunches.

 In addition to following standard performance tuning standards, it is necessary to

understand the particular effect on the server or database on typical operations. This

enables you to monitor and manage unpredictably changing performance

characteristics.
 References

Casazza, J. P., Greenfield, M., & Shi, K. (2006). Redefining server performance

characterization for virtualization benchmarking. Intel Technology Journal, 10(3).

Decusatis, C. J. S., Carranza, A., & DeCusatis, C. M. (2012). Communication within clouds:

open standards and proprietary protocols for data center networking. IEEE

Communications Magazine, 50(9), 26-33.