#001 Building Your Sandbox
This week I've moved DBA Challenges to a new platform. You can find all previous editions at Blog (automatesql.com).
I'm also trying a new strategy. Proposing a weekly challenge that we all can participate in. You can think of these as mini projects to gain hands-on experience. But, to do that, you'll need to build a sandbox.
Estimated time to complete: Less than 8 hours.
What you will learn by completing this challenge.
- Reviewing hardware specifications.
- Hypervisors - Differences in type 1 and type 2. Installation.
- Simple virtual networking
- Windows Server installation
- Creating virtual machines
Step 1: Identify Hardware For the Host
Since we're using a virtual environment you'll need to ensure the machine supports virtualization. There are four key areas to review:
Processor - The CPU needs to be an x64 processor. Newer Macs, containing the new M series processors, won't work for the environment we're building. Windows Server isn't compatible.
The processor must also support virtualization. You can review the specifications for your processor at the manufacturer's website or check the CPU tab in Task Manager on Windows. Check the following links to determine if your host machine CPU supports virtualization.
For AMD processors, find your processor model and then check the specifications. AMD-V should be listed as a supported extension.
I'd also recommend you use a multi-core processor.
Memory - Your host should have enough memory to support multiple virtual machines. At least 16 GB. The more the better.
Storage - At least 256 GB of free space to support multiple machines. The environment we're building will contain various virtual machines.
Operating System - Ubuntu, Red Hat, or Windows 11 can all be used as the host operating system. I use Windows 11 Pro.
Step 2: Selecting a Hypervisor
Next up, select a hypervisor. There are two types of hypervisors;
- Type 1 - runs directly on physical hardware without a separate operating system. These are commonly referred to as bare-metal hypervisors. Proxmox and VMware ESXi are two examples of this type.
- Type 2 - runs as a software layer on an operating system. This is ideal if you use a multi-purpose machine to host your environment. Here are two free type 2 hypervisors:
I've used both, but I find VMware Workstation Pro easier.
Step 3: Downloading ISOs
Next, you'll need to download the ISO for Windows Server 2022. We'll use the evaluation edition. This edition can be used for up to 180 days but can be extended.
You'll also need to grab the SQL Server 2022 Developer Edition ISO.
Step 4: Creating Your Virtual Machines
Create two Windows Server 2022 virtual machines on the same virtual network. The network type should be host-only or NAT. Steps to create this network will vary depending upon the hypervisor you've chosen.
Host-only will only permit network communication between the host and the virtual machines (i.e. the VM won't be able to reach the internet).
NAT will allow your virtual machines to connect to the internet.
- DC1 - This one will be used as the domain controller and DNS. A 40 GB drive should be all that is needed.
- SRV1 - This will be your first client machine. A 40 GB drive will work here as well. Additional disks can be attached later.
Complete the Windows Server 2022 Standard Evaluation (desktop experience) installation and install any virtualization guest utilities (VMware tools or VirtualBox guest additions). It would be a good idea to go ahead and install any available updates, rename the VM hostnames to DC1 and SRV1, and set the VMs to use the correct timezone.
Helping Others and Sharing Your Results
That's it for this week. If you have tips other readers can learn from, please share them in the comments. You can message me on LinkedIn or post about it and tag me with the #dbachallenges hashtag.
Feedback
If there's a DBA Challenge you'd like to see, please let me know by replying to this email. Have ideas on how to make these more useful? I'd love to hear those too.
Good luck and I'm looking forward to seeing your results!
Luke
Responses