A Fine Slice Of SQL Server
Here is the start of the function. I validate the VMName parameter to ensure that there a VM with that name does not already exist
Before Rob’s posts, I hadn’t seen Pester before, but if you write a lot of Powershell code, it looks like a nice testing framework.
Comments closedEd Elliott continues to amaze me. This time, he’s got a code coverage tool for T-SQL code:
If we execute this stored procedure we can monitor and show a) how many statements there are in this and also b) which statements have been called but we can’t see which branches of the case statement were actually called. If it was a compiled language like c# where we have a profiler that can alter the assembly etc then we could find out exactly what was called but I personally think knowing which statements are called is way better than having no knowledge of what level of code coverage we have.
Yet another reason to grab the SSDT Dev Pack. By this point, I expect there to be a couple more reasons next week…
Comments closedAdam Machanic has made the SQLQueryStress source code publicly available:
So here’s the official word: The attached source code is hereby released to the world, copyright and royalty free. You may use it, if you like, for whatever you want. Enjoy! If you use it for a public project, I would appreciate a mention in the acknowledgements section, but even that is not required. This source code is yours, warts and all. I was tempted to do some cleanup work, but at this point it’s just not something I’m ever going to touch again. I upgraded the project from Visual Studio 2005 to Visual Studio 2013, confirmed that it builds and seems to work, and that’s that.
Adam may never have used in a production scenario, but I certainly have, and SQLQueryStress is still the best free load simulator. There’s also a GitHub repo thanks to Erik Ejlskov Jensen, so go forth and hack at some C# code.
Comments closed