Загрузка...

most common interview question #tech #backend #systemdesign #gratitude #fyp #shortvideo #ytshorts

This is a very common but tricky SQL interview question.

Why is deleting many rows slower than TRUNCATE in SQL?

1 DELETE removes rows one by one Each row deletion is logged individually. Indexes are updated for every row.

2 TRUNCATE removes data at once It deallocates entire data pages. No row-by-row processing.

3 Logging difference

DELETE generates heavy transaction logs. TRUNCATE logs minimal metadata changes.

4 Trigger & constraint behavior DELETE fires triggers and checks constraints. TRUNCATE usually does not.

5 Rollback impact

DELETE can be rolled back normally. TRUNCATE behavior depends on DB engine
Interview takeaway

DELETE = row-by-row operation. TRUNCATE = bulk structural operation.

More logging + more index updates = slower DELETE.

{ SQL, Databases, QueryOptimization, BackendEngineering, InterviewPrep, Performance }
Save this for interviews
#techdevelopers #devlife #fullstackdev #codingrules #codingblog #codingsecrets #codingsuccess #dailydev
Share with a frontend or backend dev Follow for system design & full-stack fundamentals

#codinginterview #cleancoder #technicalinterview #codebuild #techinterviews #techinterview #keepcoding #codecareer #codementor #coderush

[software, coder, developer, frontend developer, backend engineering, system design, interview prep, software engineer, computer networks, computer science, cs students, programming, coding, web development, internet basics, tech reels, learn in public, FAANG, google, hiring, interviews, tips]

Видео most common interview question #tech #backend #systemdesign #gratitude #fyp #shortvideo #ytshorts канала TechKiKahani
Яндекс.Метрика
Все заметки Новая заметка Страницу в заметки
Страницу в закладки Мои закладки
На информационно-развлекательном портале SALDA.WS применяются cookie-файлы. Нажимая кнопку Принять, вы подтверждаете свое согласие на их использование.
О CookiesНапомнить позжеПринять