Building code that executes a program and redirects the standard output and standard error seems like an easy task when you have access to .NET.
At first glance it is as simple as:
var startInfo = new ProcessStartInfo("C:\\Windows\\System32\\diskperf.exe","/?") { RedirectStandardOutput = true, RedirectStandardError = true, UseShellExecute = false }; using (var process = Process.Start(startInfo)) { if (process.WaitForExit(100)) { Console.WriteLine(process.StandardOutput.ReadToEnd()); } } Which seems like the appropriate way of doing this, execute process, wait for it to finish and then read the output.
I wanted to see if enabling iSER for my ESXi servers would improve the performance of iSCSI, since RDMA should offload a lot of cpu cycles.
Unfortunately it is not just a matter of checking a checkbox in ESXi to get it enabled and working, and even if you do all the required steps - it might just not work anyway.
For my Melanox ConnectX-3 (non pro) I had to this on my ESXiinstallation(s)
I have been using ESXi and VSphere for a couple of years now and have been hosting my virtual machines on a NFS datastore backed by ZFS - so in the beginning I was relying on ZFS replication + snapshots for my backup purposes which is pretty great since I could just mount a snapshot and move a specific VM to its correct location in case I wanted to restore something.
I have decided to fork Rhino Mocks and continue development of it under another name: Mammock.
Don't ask me how I came up with the name, it's kind of silly. A combination of Mammoth and Mock, but it turns out that mammock actually means something that is a fragment of something else, and you could say that a mock is a part of something else, which is the piece of code you want to test and thus Mammock is not such a bad name after all :-)
I am sure everyone have had the "pleasure" of having to maintain configuration files across projects and even solutions, only to copy and paste configuration data between them, to keep them in sync, and have had the same issues that everyone else has had. i.e. Missing variables in one project, missing sections and so forth.
So have I, and in my previous work we used Nant and a custom built script to transform our app.
Sometimes when trying to truncate a table you need to remove all foreign keys referencing that table and that can be hard to do, since you cannot get a nice graphical overview.
To get the list of foreign key constraints for a given table you can run the following script exchanging the value in the @TABLENAME parameter.
DECLARE @TABLENAME VARCHAR(100); SET @TABLENAME=''; SELECT K_Table = FK.TABLE_NAME, FK_Column = CU.COLUMN_NAME, PK_Table = PK.
When compacting large databases in SQL Server, whether or not its done via the DBCC SHRINKDATABASE command or done via the SQL Server Management Studio, you will experience a very long delay in the command returning.
To check how the process is going, you cannot simply look at a progress bar or se a percentage some nice place.
But you can use the system views in SQL Server to see how its going.
Today Amazon announced their next gen nosql db called DynamoDB.
I can't wait to get around playing with it.
I have tried using SimpleDB, and that was a mixed bag of pleasure and pain.
I hope DynamoDB will be more pleasure than pain.
Stay tuned for when I share my experience.
http://aws.amazon.com/DynamoDB//188-0664881-5201236/
