A locally hosted (on-premises) database system runs on hardware that your organization owns or leases and physically controls — servers in a rack, in a closet, or in a data center you rent space in. Everything from the power supply and network cabling to the operating system, the database engine, patching, backups, and user security sits with your team. That total ownership is the defining characteristic of local deployment, and it is the baseline against which every cloud database service in this module is compared.
This matters in COP4708 because deployment choice shapes real decisions: how you budget (large up-front capital purchases plus ongoing staffing, versus metered monthly bills), how you scale (buying and installing more hardware, versus resizing an instance in a console), and who is accountable when a disk fails at 2 a.m. Local deployment is still the right answer in many situations — strict data residency rules, low-latency industrial or lab workloads, legacy applications, and environments with poor or no internet connectivity — so understanding it well is not just historical background.
As you watch the videos below, keep a running list of tasks that a human has to perform on a local system: provisioning hardware, installing and configuring software, monitoring, applying updates, arranging redundancy, and testing recovery. Note where each of those tasks goes when the same workload moves to a managed cloud service. Also pay attention to cost: notice which costs are visible (hardware, licenses) and which are hidden (staff time, downtime, spare capacity bought "just in case").
Episode 3 of Microsoft's On Prem To The Cloud series, in which Abel Wang and Damian Brady discuss why DevOps practices matter for applications still running on on-premises infrastructure and walk through setting up a pipeline for one. The discussion surfaces the operational burden that local deployments place on a team — builds, deployments, configuration, and consistency — before any cloud migration is considered.
It frames local hosting from a practitioner's maintenance and operations perspective, which maps onto the management responsibilities subtopic, and it comes from an official Microsoft DevOps channel with credible, current practice.
Episode 7 of the same series focuses specifically on moving an on-premises application's database to Azure SQL, aimed at viewers who want getting-started material on migration. Expect discussion of what the existing local database looks like, what changes when the database becomes a managed service, and the practical steps involved in the move.
The side-by-side of a local database and its managed Azure SQL counterpart is exactly the contrast this topic is built around, making it useful for seeing which administrative duties stay with you and which shift to the provider.
A hands-on consumer and enthusiast look at repurposing an older desktop computer as a working server, from the channel's sponsor-supported remote monitoring and management angle. Expect coverage of selecting and preparing the hardware, installing server software, and the ongoing need to monitor and manage the machine once it is running. It illustrates, at small scale, what it actually means to own and operate your own infrastructure.
It makes the abstract idea of "on-premises" concrete and physical, which directly supports the subtopics on infrastructure setup, configuration, and ongoing management responsibilities. Linus Tech Tips is a well-produced, widely viewed technology channel, and the scaled-down example keeps the focus on the responsibilities rather than enterprise procurement details.
Together these videos build the on-premises half of the comparison the module requires. The Linus Tech Tips build grounds MO1 by showing the physical infrastructure characteristics that define local deployment, and it exposes the hardware purchases, spare capacity, and hands-on upkeep that feed the capital-expenditure and total-cost-of-ownership reasoning in MO2 as well as the hardware-bound scaling limits in MO3. The two On Prem To The Cloud episodes supply the operational side: episode 3 catalogs the maintenance, deployment, and reliability work an organization must absorb when it hosts its own systems, supporting the trade-off evaluation in MO4, while episode 7's Azure SQL migration makes visible which of those duties transfer to a provider and which remain with the customer — the core distinction behind the shared responsibility model in MO5.
These videos were chosen from YouTube on October 2, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.