Skip to main content

SQL : DML Commands



For freshers venturing into the realm of databases, comprehending Data Manipulation Language (DML) commands is akin to unlocking the ability to interact with and transform data within the database. This blog post seeks to provide a beginner-friendly understanding of DML commands, shedding light on their significance and practical applications using MS SQL snippets.

Background: What is DML?

DML (Data Manipulation Language) is a subset of SQL that focuses on the manipulation of data stored in a database. It includes commands for inserting, updating, and deleting data, allowing users to interact with the contents of their databases.

The DML Command Ensemble

INSERT: Introducing New Entries

The INSERT command is akin to adding new entries to a database. Suppose you want to add a new employee to the Employees table
INSERT INTO Employees (FirstName, LastName, Salary)
VALUES ('John', 'Doe', 50000.00);
 

UPDATE: Making Revisions

The UPDATE command allows users to modify existing records. If an employee's salary needs adjustment
UPDATE Employees
SET Salary = 55000.00
WHERE EmployeeID = 1;
 
Real-World Analogy: Editing a Document

Consider the UPDATE command as editing a document; you make changes to specific sections without rewriting the entire content.

DELETE: The Vanishing Act

The DELETE command removes specific records from a table. If an employee leaves the company
DELETE FROM Employees
WHERE EmployeeID = 1;
 

Real-World Analogy: Removing a Page

Imagine the DELETE command as removing a page from a notebook; the information is gone, but the notebook structure remains.

Conclusion

In the vast landscape of database management, DML commands serve as the storytellers, allowing users to not only read but actively shape the narrative of their data. Understanding and wielding these commands empower freshers to navigate and manipulate the intricate threads of information stored within databases.

As you embark on your journey with DML commands, envision them as your tools for crafting and refining the tales your data tells. 

Happy Querying!
Labels:

Comments

Post a Comment

Popular posts from this blog

Implementing and Integrating RabbitMQ in .NET Core Application: Shopping Cart and Order API

RabbitMQ is a robust message broker that enables communication between services in a decoupled, reliable manner. In this guide, we’ll implement RabbitMQ in a .NET Core application to connect two microservices: Shopping Cart API (Producer) and Order API (Consumer). 1. Prerequisites Install RabbitMQ locally or on a server. Default Management UI: http://localhost:15672 Default Credentials: guest/guest Install the RabbitMQ.Client package for .NET: dotnet add package RabbitMQ.Client 2. Architecture Overview Shopping Cart API (Producer): Sends a message when a user places an order. RabbitMQ : Acts as the broker to hold the message. Order API (Consumer): Receives the message and processes the order. 3. RabbitMQ Producer: Shopping Cart API Step 1: Install RabbitMQ.Client Ensure the RabbitMQ client library is installed: dotnet add package RabbitMQ.Client Step 2: Create the Producer Service Add a RabbitMQProducer class to send messages. RabbitMQProducer.cs : using RabbitMQ.Client; usin...
Post a Comment
Read more

Clean Architecture: What It Is and How It Differs from Microservices

In the tech world, buzzwords like   Clean Architecture   and   Microservices   often dominate discussions about building scalable, maintainable applications. But what exactly is Clean Architecture? How does it compare to Microservices? And most importantly, is it more efficient? Let’s break it all down, from understanding the core principles of Clean Architecture to comparing it with Microservices. By the end of this blog, you’ll know when to use each and why Clean Architecture might just be the silent hero your projects need. What is Clean Architecture? Clean Architecture  is a design paradigm introduced by Robert C. Martin (Uncle Bob) in his book  Clean Architecture: A Craftsman’s Guide to Software Structure and Design . It’s an evolution of layered architecture, focusing on organizing code in a way that makes it  flexible ,  testable , and  easy to maintain . Core Principles of Clean Architecture Dependency Inversion : High-level modules s...
Post a Comment
Read more

How Does My .NET Core Application Build Once and Run Everywhere?

One of the most powerful features of .NET Core is its cross-platform nature. Unlike the traditional .NET Framework, which was limited to Windows, .NET Core allows you to build your application once and run it on Windows , Linux , or macOS . This makes it an excellent choice for modern, scalable, and portable applications. In this blog, we’ll explore how .NET Core achieves this, the underlying architecture, and how you can leverage it to make your applications truly cross-platform. Key Features of .NET Core for Cross-Platform Development Platform Independence : .NET Core Runtime is available for multiple platforms (Windows, Linux, macOS). Applications can run seamlessly without platform-specific adjustments. Build Once, Run Anywhere : Compile your code once and deploy it on any OS with minimal effort. Self-Contained Deployment : .NET Core apps can include the runtime in the deployment package, making them independent of the host system's installed runtime. Standardized Libraries ...
Post a Comment
Read more