Performance monitoring SQL Server connections // IT Management Solutions

Performance monitoring SQL Server connections

db3.fwFollowing SQL database performance best practices and monitoring the health of you Connect database will help to insure a responsive Connect server providing excellent end user experience.

It is best to always place the operating system, data and log directories on separate disk drives; this will result in improved performance. If you must put Connect on the same server as the DB (never a best practice but sometimes a practical necessity), you should ensure that the Connect installation and content directories are on a different disk drive than is the database data. The Temp DB should also be on a separate disk drive. Putting the SQL data on striped disks, provides a tuning benefit as well.

db4.fwBe sure to aggressively re-index and update statistics. De-fragment the operating system data and log files on a regular schedule. Ensure that there is minimal latency between the Connect server and the SQL Server. Be wary of network maintenance and backups that can produce latency between the Connect server and the SQL server and be sure to avoid heavy Connect use during any such maintenance.

db5.fwMake sure that the SQL server has plenty of RAM; the more RAM the better. Everything works much faster in memory. The more of the database that you can keep in memory the better off you will be. Only virtualize the DB server if absolutely required.While Connect runs fine on supported VMWare servers, the SQL database server is best run on a dedicated platform

With reference to the use of separate disks, here is a prioritized list of what should have its own disk:

  1. Operating System
  2. Adobe Connect (Separate Server if possible)
  3. SQL database
  4. Data
  5. Log
  6. TempDB
  7. Transaction logs

db6.fwFor best performance, set the initial size of the transaction log file based on estimated use. This avoids unnecessary fragmentation. The transaction log should be on a different drive than is your data file, temp database and operating system. Manually shrink the transaction log files based on monitoring. If you try to do this as a nightly or weekly job, you will end up with unnecessary fragmentation. De-fragment the transaction log file as necessary and consider putting transaction logs on striped disks. Ensure regular backups as transaction log backups empty the space inside the log file and prevent it from continuing to grow.

You might also like

AntiVirus vs Antispyware vs "Security Suites"

by dmrcasf

One thing first: You stated: "... or have multiple AV programs in order to catch all possible problems."
It is actually never a good idea to have more than one Anti-Virus program actively running at one time; their actions can conflict with each other, causing crashes, hangs, and other problems. Note that this is NOT true of Anti-Spyware programs (also called "Anti-Malware" programs)- having more than one antispyware program monitoring your system is a Good Thing.
Remember that your McAfee Security Suite contains not only an anti-virus program, but also an antispyware program, a firewall, and a few other security/privacy-protection tools

McGraw-Hill Osborne Media IBM Cognos Business Intelligence 10: The Official Guide
eBooks (McGraw-Hill Osborne Media)

Senate panel OKs $51 billion for Commerce, Justice, Science  — FCW.com
One sticking point is the House's desire to limit funding for the National Strategy for Trusted Identities in Cyberspace, a plan designed to come up with a new system for managing identities online.

Related Posts



Copyright © . All Rights Reserved