SQL Server 2022 DBA 홈 랩 구축 가이드

올바른 설정과 구성을 통해 SQL Server 2022 DBA 홈 랩을 빠르고 효율적으로 구축할 수 있습니다.

### 10분 만에 SQL Server 2022 DBA 실시간 홈 랩 구축하기
* 💻 SQL Server 2022 DBA 실시간 홈 랩을 만들려면 **BIOS가 개인화를 지원**하며 하드웨어가 요구 사항(**인텔 CPU, 최소 12GB RAM, 2.5GHz 프로세서, 최소 500GB 하드 디스크, 성능 향상을 위해 SSD가 권장됨**)을 충족하는지 확인합니다.
* 🖥 소프트웨어 측면에서는 **Windows 7, 8 또는 10과 같은 64비트 운영체제**가 필요하며, 특히 **Windows 7은 빌드 버전 17 이상**이 필요하고 필요한 설치 키는 **Google 드라이브 링크**를 통해 제공됩니다.
* 🛠 이 설정에는 **4개의 가상 머신**이 포함되는데, 하나는 **Active Directory용**, 다른 3개는 **SQL Server 멤버 서버**로 사용되며, 첫 번째 노드는 복제 프로세스 중에 발생하는 **메모리 문제를 해결하기 위해 4GB RAM**으로 구성됩니다.
* 🔧 VMware Workstation 17.5를 설치한 후 **Google 드라이브에서 가상 머신 파일을 다운로드**하여 추출하고 필요한 네트워크 설정 및 어댑터로 각 머신을 올바르게 구성해야 합니다.
* 📊 이 구성에는 **190일마다 자동 갱신**을 위한 KMS 설치와 로그 전송, 미러링 및 복제를 위한 **기본 인스턴스 설정**이 포함되어 있으며, 모두 **플러그 앤 플레이 방식**으로 쉽게 사용할 수 있도록 설계되었습니다.
* 🔄 재시작 후 DNS 설정이 루프백 주소로 되돌아갈 수 있으므로 **DNS 설정을 확인**하고 권한 문제를 방지하기 위해 **모든 노드에 글로벌 관리자 자격 증명이 일관되게 적용**되는지 확인해야 합니다.
* ⚙ 가상 머신의 전원이 올바른 순서로 켜지면 **각 노드를 핑하여 연결을 확인**하고 상시 가동 가용성 그룹, 미러링 및 클러스터링에 대한 모든 구성이 올바르게 설정되어 있는지 확인합니다.
* 💡 일반적으로 약 **5,000루피의 비용**이 드는 이 실험실 설정은 무료로 제공되며, 피드백이나 링크 요청은 이메일을 통해 제출하거나 설명 상자에서 확인할 수 있습니다.

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

MS SQL DBA Tech Support

SQL Server 2022 DBA 실시간 홈 랩 구축하기

실습실을 설정하려면 BIOS가 개인 설정을 지원하고 12GB RAM, 2.

5GHz 프로세서 및 500GB 하드 디스크가 장착된 인텔 CPU를 사용해야 합니다.

소프트웨어 요구 사항에는 64비트 OS가 포함되며, Windows 7, 8 또는 10이 가장 이상적입니다.

실습 환경은 메모리 문제를 해결하기 위해 2GB 및 4GB RAM을 사용하는 4대의 컴퓨터로 구성되며, 한 대는 Active Directory로, 다른 한 대는 SQL Server 멤버 서버로 사용됩니다.

Google 드라이브에서 가상 머신 설정

Google 드라이브에서 모든 가상 머신 파일을 다운로드하여 DC 폴더에 압축을 풉니다.

가상 머신을 시간 순서대로, DC부터 시작하여 노드 1, 노드 2, 노드 3 순으로 엽니다.

활성 디렉터리의 DNS 설정을 모니터링하고 모든 인스턴스에 대해 기본 관리자 자격 증명을 사용하세요.

글로벌 관리자 설정 및 노드 구성하기

권한 문제를 피하기 위해 글로벌 관리자 사용자 계정을 만들 수 있습니다.

노드 간의 통신을 확인하고 서로 핑이 성공적으로 이루어지고 있는지 확인하는 것이 중요합니다.

상시 미러링 및 노드 복제를 위한 구성이 설정되어 있으며, 수동 종료로 인한 오류는 실용적인 목적을 위해 무시해야 합니다.

SQL Server용 상시 가동 클러스터 설정하기

상시 가동 클러스터를 만들려면 하드 디스크를 추가하고 SQL Server 설치를 위해 클러스터와 공유하세요.

이 실습은 간단하고 공간 효율적으로 설계되어 모든 실용적인 사항을 다룹니다.

이 이니셔티브는 피드백 요청과 링크 공유를 위한 이메일 ID와 함께 무료로 제공됩니다.