Discussion on the parts you can (and sometimes need to) kick.
Now we get to the meat of the matter. You want a virtual cluster, the first thing you have to do is create your own portable domain. Start with a plain vanilla install of Windows 2003 R2 Standard on a semi-default VM. (1 GB RAM, 2 cores, 2 NICs, 128GB dynamically expanding VHD file). I chose this because it had the smallest disk and memory footprint of any current supported Microsoft Server product. I created the VM with a single dynamically expanding VHD, one fixed 16 GB VHD, and two NICs. One NIC is connected to the outside world...
Denny Cherry tagged me to write about my best MacGyver Moment. Usually I ignore blogosphere fluff and just use this space to write what I think is important. However, #MVP10 just ended and I have a stronger sense of community. Besides, where else would I mention my second best Macgyver moment was making a BIOS jumper out of a soda can. Aluminum is conductive and I didn't have any real jumpers lying around.
My best moment is probably my entire home computer network.
Every system but one is hand-built, usually cobbled together out of spare parts and 'adapted' from its original...
This past Saturday I enjoyed the hospitality of the Tampa SQLSaturday (#32) team. My presentation was “Clustering for Mere Mortals”. Unlike many clustering presentations, I had demonstration content. This resulted in the most asked question being “Do you have instructions on how you built that?” This is the first part of those instructions.
Here is what the cluster consists of (Virtually):
One Windows 2003 R2 (x64) Server acting as Domain Controller, DNS Server, DHCP Server, File Server and iSCSI Target Server
Two Windows 2008 R2 Servers as cluster Nodes.
All this runs on a Lenovo W500 laptop with an Intel Core 2 Duo T9600...
Anyone who has spent time in the computer business and has some grasp of hardware issues understands fragmentation. For those whose concept of hardware is limited to “it’s the part I can kick”, here is a quick and painless overview.
I like analogies so let’s think of a disk drive as a very large, tall building having many rooms and many floors. The disk head is you. Your task is to run around and “read” something from particular rooms (blocks). A simple thought exercise would suggest it is easier to read rooms “in order” on a floor rather than scattered...
Looks like the Great Zune Massacre of 2008 was a day 366 issue. Again, someone forgot to throw out the code from the lowest ten percent of the Stack-Rank system. Sorry to sound harsh, but this is type of thing will flunk you out of Programming 101. I don't even want to get started on the QA failure, but it is even worse.
Semi-Kudos to the Zune Team. There was a notice on the support page shortly after the original post acknowledging the problem and indicating they were working on it. Microsoft also got word out through its MSNBC subsidiary as...
Yes, I own a 30 GB Zune. Yes, it crashed today. Yes, I am unhappy.
Having worked in the computer industry for many years now, I watched many companies deal with failed products. Such is inevitable in an industry that gives the biggest rewards to the first implementation that is “good enough”. More importantly, I have seen companies deal with failures in various ways. Some handled things well and some no longer exist or have lost market dominance due to poor reactions to failures. Here are a few observations that I am sure Microsoft will ignore, partly because you have to...
Fast on the heels of SQL 2008 is the Feature Pack for SQL 2008. Cool goodies include stand-alone installers for SQLCMD and the SQL Native Client, SQL 2008 Server Management Objects, SQL 2008 pre-defined Policies, and lots more.
You can find it here.