Select Page

Building a SQL Server Virtual Lab in Windows: Configuring VMs for the SQL Servers

JP Chen | | July 16, 2020

In my previous blog post, Create VMs for the SQL Servers, we had created a VM, installed Windows Server 2019 and SQL Server 2019, enabled TCP/IP, configured Windows Firewall, and then cloned the VM to create two new VMs. We had also renamed the labels for the VMs as DV-SQL01, DV-SQL02, and DV-SQL03 in Oracle VM VirtualBox Manager.

Now, we will configure the VMs to assign static IP addresses to the VMs, rename the VMs and join the DV-SQLNET domain, rename the SQL Server instances in each of the VMs, and update the SQL Server and SQL Server Agent Service Accounts to use the domain user accounts we had created.

Assigning Static IP Address to the VMs

Back in IP Address, Subnet Mask, and Default Gateway, we had pointed out that every device connected to a network needs an IP address to communicate. Static IP addresses are a better choice than dynamic IP addresses for servers that need constant access and enables you to reach the servers without the IP addresses getting changed. We had assigned a static IP address for DV-DC VM back in Assigning Static IP Address for the DC VM, we will now assign static IP addresses to DV-SQL01, DV-SQL02, and DV-SQL03.

Table 2-4 IP Addresses for the Servers in the Virtual Lab documents each server’s IP address, Subnet Mask, Default Gateway, Preferred DNS Server, and Alternate DNS Server. The Subnet Mask is the same for all servers. The Preferred DNS Server for the DV-DC server is 127.0.0.1 pointing back to itself as it’s serving as the DNS Server for the domain. All other servers in the domain will have the Preferred DNS Server pointing to 192.168.0.20 as it’s the DNS Server. The Alternate DNS Server is pointed to Google DNS Server for all.

Table 2-4 IP Addresses for the Servers in the Virtual Lab

Server IP Address Subnet Mask Default
Gateway
Preferred
DNS Server
Alternate DNS Server
DV-DC 192.168.0.20 255.255.255.0 192.168.0.1 127.0.0.1 8.8.8.8
DV-SQL01 192.168.0.21 255.255.255.0 192.168.0.1 192.168.0.20 8.8.8.8
DV-SQL02 192.168.0.22 255.255.255.0 192.168.0.1 192.168.0.20 8.8.8.8
DV-SQL03 192.168.0.23 255.255.255.0 192.168.0.1 192.168.0.20 8.8.8.8

 

To assign static IP Address to the DV-SQL01, DV-SQL02, and DV-SQL03:

  1. Click DV-SQL01 to select it on Oracle VM VirtualBox Manager.
  2. Click Start to start it.
  3. Logon to the DV-SQL01 VM.
  4. Open Server Manager if not auto started.
  5. Click Local Server on the left pane of Server Manager.
  6. Click the link for Ethernet as shown in Figure 2-33 Opening the IP V4 Properties.
  7. Right-click on Ethernet in the Network Connections folder.
  8. Click Properties on the pop-up menu.
  9. Click Internet Protocol Version 4 (TCP/IPv4).
  10. Click Properties.

    Figure 2-33 Opening the IP V4 Properties

  11. Click the option button for Use the following IP address as shown in Figure 2-34 Assigning Static IP to the DV-SQL01 VM.
  12. Type 192.168.0.21 in the IP address field.
  13. Press Tab on your keyboard.
    You will notice the Subnet mask field is auto populated with 255.255.255.0.
  14. Type 192.168.0.1 in the Default gateway field.
  15. Press Tab on your keyboard twice to move to the Preferred DNS server field.
  16. Type 192.168.0.20 in the Preferred DNS server field.
    This is the IP address of the DC where it also has the DNS sever role installed.
  17. Press Tab on your keyboard.
  18. Type 8.8.8.8 in the Alternate DNS server field.
    We will use the Google DNS Server.

    Figure 2-34 Assigning Static IP to the DV-SQL01 VM

  19. Click OK.
  20. Click Close.
  21. Close the Network Connections folder.
  22. Click the Oracle VM VirtualBox Manager on the host computer taskbar.
  23. Click DV-SQL02 to select it on Oracle VM VirtualBox Manager.
  24. Repeat steps 2 to 21 to assign static IP Address to DV-SQL02.
    Check Table 2-4 IP Addresses for the Servers in the Virtual Lab for the IP address, Subnet Mask, Default Gateway, Preferred DNS Server, and Alternate DNS Server for DV-SQL02.

    When completed, the Internet Protocol Version 4 (TCP/IPV4) Properties dialog box should look like Figure 2-35 Assigning Static IP to the DV-SQL02 VM.

    Figure 2-35 Assigning Static IP to the DV-SQL02 VM

  25. Click the Oracle VM VirtualBox Manager on the host computer taskbar.
  26. Click DV-SQL03 to select it on Oracle VM VirtualBox Manager.
  27. Repeat steps 2 to 21 to assign static IP Address to DV-SQL03.
  28. Check Table 2-5 IP Addresses for the Servers in the Virtual Lab for the IP address, Subnet Mask, Default Gateway, Preferred DNS Server, and Alternate DNS Server for DV-SQL03.
    When completed, the Internet Protocol Version 4 (TCP/IPV4) Properties dialog box should match Figure 2-36 Assigning Static IP to the DV-SQL03 VM.

    Figure 2-36 Assigning Static IP to the DV-SQL03 VM

 
We have now assigned static IP addresses to the servers in the virtual lab. Next, we will rename them to DV-SQL01, DV-SQL02, and DV-SQL03 accordingly and then join the DV-SQLNET domain.

Renaming the VMs and Joining the DV-SQLNET Domain

The cloned VMs will inherit the computer name from the original VM. You will need to rename them to reflect their functions and differentiate them from other servers in the network. In this section, we will rename the VMs to DV-SQL01, DV-SQL02, and DV-SQL03 and join them to the DV-SQLNET domain.

You will need the domain administrator access to join the domain. For the following steps, we will use the DV-SQLNET\Administrator account.

To rename the VMs and join the DV-SQLNET domain:

  1. Click the DV-SQL01 VM on the task bar as shown in Figure 2-37 Clicking on the VM on the Taskbar.

    Figure 2-37 Clicking on the VM on the Taskbar

  2. Open Server Manager.
  3. Click Local Server on the left pane.
  4. Click the link for Computer name as shown in Figure 2-38 Changing the Computer Name and Joining Domain.
  5. Click Change.
  6. Type DV-SQL01 in the Computer name text box.
  7. Click the option button for Domain.
  8. Type DV-SQLNET.COM in the Domain text box.

    Figure 2-38 Changing the Computer Name and Joining Domain

  9. Click OK.
  10. Type DV-SQLNET\Administrator in the User name text box.
  11. Press Tab on your keyboard.
  12. Type Password$ in the Password text box.
  13. Click OK.
  14. Click OK on the Welcome to the DV-SQLNET.COM domain message box.
  15. Click OK to acknowledge you must restart your computer to apply these changes.
  16. Click Close.
  17. Click Restart Now to restart your computer.
    The VM will restart and prompt you to unlock to logon.
  18. Presse Ctrl + Delete on your keyboard.
  19. Click Other user on the lower left hand corner.
  20. Type DV-SQLNET\Administrator in the User name text box.
  21. Press Tab on your keyboard.
  22. Type Password$ in the Password text box.
  23. Press Enter on your keyboard.
    You are then logged on to the DV-SQLNET domain with the Domain Administrator account.
  24. Open Server Manger if it’s not auto started.
  25. Click Local Server on the left pane.
  26. Notice the Computer name and Domain fields are updated as shown in Figure 2-39 Viewing the Computer name and Domain.

    Figure 2-39 Viewing the Computer name and Domain
    This completes the renaming step for DV-SQL01 and joining the DV-SQLNET domain. We will continue onto renaming DV-SQL02 and joining the domain in the next steps.

  27. Click the DV-SQL02 VM on the task bar.
  28. Repeat steps 2 to 25 to rename the VM to DV-SQL02 and join the DV-SQLNET.COM When completed, check the Local Server Properties page and it should show the Computer name as DV-SQL02 and Domain as DV-SQLNET.COM.
  29. Click the DV-SQL03 VM on the task bar.
  30. Repeat steps 2 to 25 to rename the VM to DV-SQL03 and join the DV-SQLNET.COM When completed, check the Local Server Properties page and it should show the Computer name as DV-SQL03 and Domain as DV-SQLNET.COM.

Renaming the SQL Server Instances

Like the server names of which were inherited from the original VM, the SQL Server instance too are copied over to the clones. In this section, we will run a script to update them to reflect their actual server names and create a domain login for the SQL DBA, Jack Bauer, and add him to the sysadmin server role.

Updating the SQL Server instance name requires two steps. First, you will need to drop the server using the SP_DROPSERVER stored procedure and then use the SP_ADDSERVER stored procedure to add the correct server.

Creating a domain login for the SQL DBA and adding the login to the sysadmin server role can be done via the CREATE LOGIN and ALTER SERVER ROLE T-SQL statements.

To rename the SQL Server instance name for DV-SQL01, DV-SQL02, and DV-SQL03 and create a domain SQL Login as a sysadmin:

  1. Click the DV-SQL01 VM on the task bar.
  2. Logoff the Domain Administrator user.
  3. Logon to DV-SQL01 using the local administrator.
    You can click Other user on the lower left-hand corner and then type in Administrator in the User name text box and Password$ in the password text box as shown in Figure 2-40 Logging on Using the Local Administrator. Notice that we are signing in to DV-SQL01, the local server, not the domain.

    Figure 2-40 Logging on Using the Local Administrator

  4. Open SSMS.
  5. Type localhost on the Server name text box.
  6. Press Enter on your keyboard.
  7. Open a New Query.
  8. Open the following Renaming Instance and Creating a Domain SQL Login as a Sysadmin.sql script:

    01 Renaming the instance name
    02 Creating a domain login and adding it to the system administrator server role
    03 DECLARE @OldInstanceName AS NVARCHAR(50),
    04 @NewInstanceName AS NVARCHAR(50)
    05
    06 SELECT @OldInstanceName = @@SERVERNAME,
    07 @NewInstanceName = 'SERVERNAME' -- Replace with the corresponding instance name
    08
    09 Renaming the instance name by dropping the old and then adding the new server name
    10 EXEC SP_DROPSERVER @OldInstanceName
    11 EXEC SP_ADDSERVER @NewInstanceName, local
    12
    13 Creating a domain login and adding it to the sysadmin role
    14 CREATE LOGIN [DV-SQLNET\JBauer] FROM WINDOWS
    15 ALTER SERVER ROLE sysadmin ADD MEMBER [DV-SQLNET\JBauer]

    Script 2-3 Renaming Instance and Creating a Domain SQL Login as a Sysadmin.sql
  9. Update ‘SERVERNAME’ on line 07 of the script to ‘DV-SQL01’ as this is to run on DV-SQL01.
  10. Run the script.
  11. This will rename the instance to DV-SQL01, create a domain login JBauer, and add the login to the sysadmin server role.
    Next, we will do the same for DV-SQL02.
  12. Click the DV-SQL02 VM on the task bar.
  13. Logoff the Domain Administrator user.
  14. Logon to DV-SQL02 using the local administrator.
    You can click Other user on the lower left-hand corner and then type in Administrator in the User name  text box and Password$ in the password text box.
  15. Repeat steps 3 to 7 on the DV-SQL02 VM.
  16. Update ‘SERVERNAME’ on line 07 of the script to ‘DV-SQL02’ as this is to run on DV-SQL02.
  17. Run the script.
    This will rename the instance to DV-SQL02, create a domain login JBauer, and add the login to the sysadmin server role.

    Next, we will do the same for DV-SQL03.

  18. Click the DV-SQL03 VM on the task bar.
  19. Logoff the Domain Administrator user.
  20. Logon to DV-SQL03 using the local administrator.
    You can click Other user on the lower left-hand corner and then type in Administrator in the User name  text box and Password$ in the password text box.
  21. Repeat steps 3 to 7 on the DV-SQL03 VM.
  22. Update ‘SERVERNAME’ on line 07 of the script to ‘DV-SQL03’ as this is to run on DV-SQL03.
  23. Run the script.
    This will rename the instance to DV-SQL03, create a domain login JBauer, and add the login to the sysadmin server role. We will update the SQL Server and the SQL Server Agent service accounts to use the dedicated domain user accounts in the next steps.

Updating the SQL Server and SQL Server Agent Services Accounts

As our SQL Server instances interact with other servers on the network for HADR, we had created domain user accounts back in Creating Domain Accounts for the SQL Server Services. Each SQL Server instance has a dedicated domain account for the SQL Server service and another for the SQL Server Agent service.

We will now update them in each of the SQL Servers.

To update the SQL Server and SQL Server Agent Services accounts on DV-SQL01, DV-SQL02, and DV-SQL03:

  1. Click the DV-SQL01 VM on the task bar.
  2. Unlock the DV-SQL01 VM.
    You are still logged on as the local administrator.
  3. Open SQL Server Configuration Manager.
  4. Click SQL Server Services on the left pane.
  5. Double-click SQL Server Agent (MSSQLSERVER).
  6. Click Browse.
  7. Click Locations…
  8. Type DV-SQLNET\Administrator in the User name text box.
  9. Press Tab on your keyboard.
  10. Type Password$ in the Password text box.
  11. Click OK.
  12. Click Entire Directory.
  13. Click OK.
  14. Type DV-SQLNET\svc_dv-sql01_sqlagent on the Enter the object name to select text area.
  15. Click Check Names.
    SQL Server authenticates and verifies with the Active Directory and underlines the DV-SQLNET\svc_dv-sql01_sqlagent account.
  16. Click OK.
  17. Type Password$ in the Password text box.
  18. Press Tab on your keyboard.
  19. Type Password$ in the Confirm password text box.
  20. Click Apply.
  21. Click Start.
    The SQL Server Agent service starts.
  22. Click OK.
  23. Double-click SQL Server (MSSQLSERVER).
  24. Click Browse.
  25. Click Locations…
  26. Type DV-SQLNET\Administrator in the User name text box.
  27. Press Tab on your keyboard.
  28. Type Password$ in the Password text box.
  29. Click OK.
  30. Click Entire Directory.
  31. Click OK.
  32. Type DV-SQLNET\svc_dv-sql01_sqlde on the Enter the object name to select text area.
  33. Click Check Names.
    SQL Server authenticates and verifies with the Active Directory and underlines the DV-SQLNET\svc_dv-sql01_sqlde account.
  34. Click OK.
  35. Type Password$ in the Password text box.
  36. Press Tab on your keyboard.
  37. Type Password$ in the Confirm password text box.
  38. Click Apply.
  39. Click Yes to acknowledge this will cause the service to be restarted.
    The SQL Server service restarts.
  40. Click OK.
    This completes updating the SQL Server and SQL Server Agent service accounts to use dedicated domain user service accounts. Next, we will do the same for DV-SQL02.
  41. Click the DV-SQL02 VM on the task bar.
  42. Unlock the DV-SQL02 VM.
    You are still logged on as the local administrator.
  43. Repeat steps 3 to 46 for DV-SQL02.
    For the SQL Server Agent service account, use DV-SQLNET\svc_dv-sql02_sqlagent.
    For the SQL Server service account, use DV-SQLNET\svc_dv-sql02_sqlde.
    Next, we will do the same for DV-SQL03.
  44. Click the DV-SQL03 VM on the task bar.
  45. Unlock the DV-SQL03 VM.
    You are still logged on as the local administrator.
  46. Repeat steps 3 to 46 for DV-SQL03.
    For the SQL Server Agent service account, use DV-SQLNET\svc_dv-sql03_sqlagent.
    For the SQL Server service account, use DV-SQLNET\svc_dv-sql03_sqlde.

 

You have now configured the VMs for the virtual lab. My final blog post next week in the series will be testing the virtual lab. Stay tuned.

If you’ve missed anything in the series, I’ve included the links below:

Virtualization Concepts

Virtual Network for the Virtual Lab

Software & Hardware Requirements

Installing Oracle VM VirtualBox and Creating a Virtual Network

Creating the Domain Controller (DC) VM

Create VMs for the SQL Servers

Subscribe to Our Blog

Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.

ORA-12154: TNS:could not resolve the connect identifier specified

Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.

Jeremiah Wilton | March 4, 2009

12c Upgrade Bug with SQL Tuning Advisor

Learn the steps to take on your Oracle upgrade 11.2 to 12.1 if you’re having performance problems. Oracle offers a patch and work around to BUG 20540751.

Megan Elphingstone | March 22, 2017

Shortcut to Fixing a Corrupted Oracle Inventory

Oracle Central Inventory files are essential to installing and patching software. The process for fixing a corrupted file can be found here.

Chad Cleveland | February 23, 2016

Work with Us

Let’s have a conversation about what you need to succeed and how we can help get you there.

CONTACT US

Work for Us

Where do you want to take your career? Explore exciting opportunities to join our team.

EXPLORE JOBS