Hello friends. Today I'm going to show you how to build an SQL Server 2022 DBA real-time home lab in 10 minutes. For this, we need to have personalization support in BIOS. If you are using an Intel CPU with 12GB RAM or more than that, a 2.5GHz processor, and a 500GB hard disk (if you have an SSD, that would be better) so that you can experience the fastness. Coming to software requirements, you need a 64-bit OS, either Windows 7, 8, or 10. They have to maintain Windows 7, 17 point, all this build version. The key was provided in the Google Drive link as well. Let me explain our environment. I am having four machines; one is an Active Directory, and the remaining all are SQL Server member servers only. Here, I have 2GB and 4GB. The reason I have given 4GB here is that I am facing one issue in the replication that the process has been

99% has been waiting and waiting for the server. I'm getting this error uh because I have trouble shot and everything and everything is fine but after I later I came to know that uh it is suffering with memory crunch so I upgraded to from 2 GB to 4 GB so that's how the issue got resolved so that's the reason the I am using node one as a main main uh primary one that's the reason I have encrypt the 4GB so if you want if you are having memory you can keep that 20 GB okay sorry 2GB and 2GB and 2GB Windows 12 ABC and Bridge this is maintenance like 50 adapter 1 2 3 and the subnet mask this is the Gateway and Gateway is very same for all the one DNS and DNS is the same thing okay and uh to all these things and this is the network after for artbit purpose okay so this is the configuration that I have used virtual machines now once you install that VM workstation 17.5 build this version so

you can go to the Google Drive and download all these virtual machines and keep them in a folder. So once you download, or once you have downloaded all these files, you just right-click or select that, you just extract to DC. So right-click, you have to do for each and everything. So extraction will take time, and so that's the reason to avoid that. I already un, I mean, I already G and everything and kept in the DB drive folder. So once you install this, open your virtual machine, like you go to D drive, select lab, select DC, select VM, click okay. So like this, you have to open everything, lab node one done, node two, node three, okay. So you have to open like this, and let's finish all this, okay. Once it is done, so here the dis, the DC and everything, everything I have configured and everything. So this is like I have installed KMS, which is auto-renewable for every 190 days. And so all are developed, developed, named developed default instance only for all the log shipping and mirroring and replication.

all based on is all everything is configured. You just ready to use like Plug and Play. Like okay so so whenever you restart the please check the DNS of the any active directory. It will set back to the to 127.0 like0 to the L back address. So just keep on this eye okay so if it is change just change to the 1 like 0.50. And the global administrator is SL ABC and administrator and password for every Global Local administr 1 23 only and all are default instance only okay. Now you just come down first open in in the Chron chronological order first power on the virtual machine. So once it is started then only you have to start with the node one. Why because so the CPU will get high and it will get struck okay. So that's reason once it is started okay see now the fan speed is getting very high. So DC so just now type here uh 1 2 3. So now it is on now you can turn on node one now node two. So make sure that uh log everywhere in

the global administrator to avoid like uh permission kind of issues. Otherwise, you can create um one Global administrator user account. You can use uh that if you want. So, this we are using for Practical purpose. Then you can utilize this one, okay? So, done. This is also done. So, now come to DC here. Uh, so whenever you restarted or anything, just uh check this adapter. So, why? Because uh this is a something uh loophole drawback in the VMware virtual versions which are installing. See, okay now it's good. Whenever restart, I mean to say okay now. Before doing anything, you check the communication like um ping node one. Yeah, it's pinging. Node two. Yeah, it's pinging. Node three. So, now issues got. I mean no issues. So, I am connecting to node one. Yeah, I have connected. Node two. So, it is done. Now I'm going to node two. See, always on standard mirroring is everything is configured. Okay, so always on is also configured. I think uh go to management, go to all on here. This is primary. Show dashboard. So, everything is good here now.

see uh for SQLs. I mean since we are develop uh like database administrator, we might see that issues, network issues, or down issues in Custer uh so don't worry about that. So like why because uh we are we suspended the virtual missions right so some somewh it will show some errors don't worry okay. Why because uh it is like uh we have manually shut down and open that right that's the reason we got these issues okay. And so don't worry about that now and make sure for practical purpose we are not like in the real time we need to troubleshoot each and everything error okay. So for now I'm just resetting then everything so that uh the cluster look somewhat healthy. So this is AG configured okay and so come to note replication right is R lication monitor so everything is configured mirroring is configured all on is configured like cluster is configured like all okay not fail over cluster normal for all sudden in the back end cluster will be there that cluster is configured so everything is configured so you just tested whatever the

experiment. Uh, you need. Okay, so if you need like, uh, always-on cluster as well, you just need, uh, add this space so that, uh, you can create one more hard disk and share the hard disk to the qu, like in the, to the cluster and install SQL server in that, like, um, so that, because, because we don't use regularly, uh, always-on clustered instances, so to like, we, our aim is like the lab should be simple and should be, uh, should be consumed less space, so that's the reason we have almost covered all the practicals and everything, so you just go through that and everything and, uh, utilize the lab as most of the guys will charge like 5,000 rupees for this lab, but as a techan person, we are giving this to free. I hope you may like our initiation. You just comment your email ID and your opinion, uh, like, uh, so that, uh, we will forward that link as well, otherwise you can find this link in the, in our description box as well. Thank you, bye.

Build MS SQL SERVER 2022 Real Time Home Lab In 10 Minutes #sqlserver #homelab

Build MS SQL SERVER 2022 Real Time Home Lab In 10 Minutes #sqlserver #homelab

스크립트