SQL Server gets a health check


SQL Server gets a health check

A Microsoft SQL Server performance analysis service has been introduced by Conchango to ensure that firms' databases are working efficiently, writes Eric Doyle.

Barrie Pike, head of business intelligence and portals at Conchango, explained that just because SQL Server appears to be running smoothly, it does not mean that it is working at optimum performance.

Conchango's Health Check takes a holistic view of the implementation to ensure that the minimum number of servers are employed and that they are tuned to suit their designated tasks. To do this, the company reviews the hardware, network, code, data models and database requirements to produce a report of short-term and long-term recommendations to improve the system.

Short-term solutions could include configuration changes and more efficient memory use, while long-term recommendations might include storage configuration, high availability or clustering.

"The starting point is to establish exactly what the customer wants to achieve with their technology," said Pike. "We can then ensure their SQL Server works as hard as possible to support their strategic goals."

Health Check also examines the number and types of databases being run and suggests ways in which the server count can be reduced.

During the beta phase of development, Conchango found one instance where changing a single CRM component resulted in customer searches that once took five seconds being completed in less than one second.
Related Topics: Server hardware, VIEW ALL TOPICS

Email Alerts

Register now to receive ComputerWeekly.com IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

COMMENTS powered by Disqus  //  Commenting policy