The tool-set discussed in this article can help spot issues to feed into decisions/direction on Database Server Sizing re: memory, disk and number of processor sizing considerations, in order to help ensure that the SES database is as responsive as needed given the size of a customer SES implementation.
Naturally, though every database should run as efficiently and effectively as possible, throughput or resource contention issues will be felt more acutely in large dataset implementations, simply due to the sheer size of the data involved.
Steps:
First - Visit the following web page:
https://sqlserverperformance.wordpress.com/2013/11/15/sql-server-diagnostic-information-queries-for-november-2013/
On it you'll find a pair of links, ordered by SQL Server Version Number (e.g. 2005, 2008... 2014, etc). The author maintains these SQL statement sets, as well as the spreadsheets into which their result sets should be copy/pasted. Note: These links are closely spaced, so each of these lines looks like a single link, but it actually contains two links.
Second: Download the SQL statement set that matches your SQL Server Version Number, using the left-most link, and keep that open in (say) notepad.
Third: Download and open the second link - the Excel spreadsheet that matches the SQL Version you're using.
Next, follow the article author's recommendations on how to run these (using SQL Management Studio, for example), after which the copy the results (with headers) into the Excel spreadsheet.
Note that each "chunk" of analytical data fetching is discrete (e.g. you cannot run the entire SQL list in one shot).
So, Copy and Paste each piece up to and including the Semi-Colon (;) that indicates the end of the SQL statement into SQL Management Studio.
Each "chunk" will be identified by a Query Number (e.g. Query 1) and a brief indication of the intention of this query (e.g. Version Info), as in the example here:
-- SQL and OS Version information for current instance (Query 1) (Version Info)
SELECT @@SERVERNAME AS [Server Name], @@VERSION AS [SQL Server and OS Version Info];
Execute the Query, then copy and paste the results (including headers) into the appropriate tab within the Excel Spreadsheet.
WinMagic has been using these queries to investigate and understand scenarios where customers are experiencing database performance issues.