We're looking to migrate our SQL Server cluster from a handful of huge boxes to a new blade with some AMD dual-core processors. The OS will be Windows 2003 I think.
We of course want to test the new implementation to make sure it performs at least as well as it did before. I think we plan to do some performance testing by hitting SQL Server directly, rather than going through an end-user's application (like a web site).
I've used LoadRunner to test a bunch of things using different protocols, but never to hit a DB directly. How much trouble is that?
Are there any other good freeware/open-source tools I should be considering?
We're fairly well grounded in performance testing in general, but could use advice re: hitting SQL Server directly.
Directly to SQLServer does pose a problem for your protocol suite. One method of doing this is to put the queries in .vbs or .wsj files and call them from a web protocol script using "system", and without doing any actual web steps in the script.
To facilitate transaction analyses, you would need to have the vbs or wsj file have access (read/write) to a separate database, for purposes of writing transaction information - name of, & time....