<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Lilllian Wanjala Chengwa</title>
    <description>The latest articles on DEV Community by Lilllian Wanjala Chengwa (@chengwalillian).</description>
    <link>https://dev.to/chengwalillian</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3524331%2Fb5be32c2-46d4-4353-a8e8-78552bd658dc.png</url>
      <title>DEV Community: Lilllian Wanjala Chengwa</title>
      <link>https://dev.to/chengwalillian</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/chengwalillian"/>
    <language>en</language>
    <item>
      <title># Snowflake and Star Schema</title>
      <dc:creator>Lilllian Wanjala Chengwa</dc:creator>
      <pubDate>Fri, 10 Oct 2025 10:52:07 +0000</pubDate>
      <link>https://dev.to/chengwalillian/-snowflake-and-star-schema-a14</link>
      <guid>https://dev.to/chengwalillian/-snowflake-and-star-schema-a14</guid>
      <description>&lt;h2&gt;
  
  
  Definitions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. A snowflake schema
&lt;/h3&gt;

&lt;p&gt;A type of data warehouse design that organizes data into a central fact table surrounded by multiple related dimension tables that are normalized—meaning they are broken down into smaller, related tables. This structure resembles a snowflake, hence the name.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. A star schema
&lt;/h3&gt;

&lt;p&gt;A type of data warehouse design that organizes data into a central fact table surrounded by denormalized dimension tables, forming a shape that resembles a star.&lt;/p&gt;

&lt;h2&gt;
  
  
  Perfomance Comparison
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Feature&lt;/th&gt;
&lt;th&gt;Star schema&lt;/th&gt;
&lt;th&gt;Snowflake schema&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Query speed&lt;/td&gt;
&lt;td&gt;Faster,fewer joins&lt;/td&gt;
&lt;td&gt;Slower,multiple joins&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Storage efficiency&lt;/td&gt;
&lt;td&gt;Lower,redundancy present&lt;/td&gt;
&lt;td&gt;Higher,normalized reduces storage&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Join complexity&lt;/td&gt;
&lt;td&gt;Low&lt;/td&gt;
&lt;td&gt;High&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Read Efficiency&lt;/td&gt;
&lt;td&gt;Optimized for ad-hoc analysis&lt;/td&gt;
&lt;td&gt;Suitable for complex hierarchical queries&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data Integrity&lt;/td&gt;
&lt;td&gt;Moderat,risk of update anomalies&lt;/td&gt;
&lt;td&gt;Higher,easier to enforce consistency&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Star schema Overview:
&lt;/h2&gt;

&lt;p&gt;The Star Schema consists of a central fact table surrounded by denormalized dimension tables, creating a star-like structure.  &lt;/p&gt;

&lt;h3&gt;
  
  
  Advantages
&lt;/h3&gt;

&lt;p&gt;Simplified queries: The structure is straightforward, making SQL queries easier and faster to write and understand.&lt;/p&gt;

&lt;p&gt;Fast retrieval: Denormalized dimensions reduce the need for complex joins, improving query performance for reporting and analytics.&lt;/p&gt;

&lt;p&gt;Better for BI tools: Many business intelligence and reporting tools are optimized for star schema designs.&lt;/p&gt;

&lt;p&gt;Intuitive model: Analysts and business users can easily understand the schema structure.&lt;/p&gt;

&lt;h3&gt;
  
  
  Disadvantages
&lt;/h3&gt;

&lt;p&gt;Redundant data: Denormalization leads to repetitive data in dimension tables, increasing storage requirements.&lt;/p&gt;

&lt;p&gt;Data integrity risks: Redundancy increases chances of anomalies if not maintained properly.&lt;/p&gt;

&lt;p&gt;Maintenance overhead: Updates to dimension values need to be managed carefully to avoid inconsistencies.&lt;/p&gt;

&lt;h2&gt;
  
  
  Snowflake schema overview
&lt;/h2&gt;

&lt;p&gt;The Snowflake Schema is a variation where dimension tables are normalized into multiple related tables, forming a tree-like structure branching out from the fact table.&lt;/p&gt;

&lt;h3&gt;
  
  
  Advantages
&lt;/h3&gt;

&lt;p&gt;Flexible hierarchies: Complex dimensional relationships can be represented clearly.&lt;/p&gt;

&lt;p&gt;Reduced storage: Normalization reduces redundancy, saving disk space for large datasets.&lt;/p&gt;

&lt;p&gt;Data Integrity: Updates are easier to manage with normalized data,reducing inconsistencies.&lt;/p&gt;

&lt;h3&gt;
  
  
  Disadvantages
&lt;/h3&gt;

&lt;p&gt;Complex queries: Joins across multiple normalized tables can complicate SQL and slow down query performance.&lt;/p&gt;

&lt;p&gt;Slower retrieval: More joins increase query execution time, which can affect reporting responsiveness.&lt;/p&gt;

&lt;p&gt;Steeper learning curve: Business users and analysts may find the structure less intuitive.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;In essence, a Star schema prioritizes simplicity and fast query performance, while a Snowflake schema focuses on optimizing storage and ensuring data consistency. The decision between the two should be guided by the organizations' specific analytical goals and operational requirements.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>What Is Row-Level Locking?</title>
      <dc:creator>Lilllian Wanjala Chengwa</dc:creator>
      <pubDate>Thu, 09 Oct 2025 08:02:51 +0000</pubDate>
      <link>https://dev.to/chengwalillian/what-is-row-level-locking-4734</link>
      <guid>https://dev.to/chengwalillian/what-is-row-level-locking-4734</guid>
      <description>&lt;h2&gt;
  
  
  Description
&lt;/h2&gt;

&lt;p&gt;Row-level locking is a mechanism that allows transactions to lock individual rows within a table, rather than locking the entire table or page. This enhances concurrency and performance by allowing multiple transactions to access different rows of the same table simultaneously without interfering with each other.&lt;/p&gt;

&lt;h2&gt;
  
  
  Uses of Row-Level Locking
&lt;/h2&gt;

&lt;h2&gt;
  
  
  1. SQL Databases
&lt;/h2&gt;

&lt;p&gt;SQL Server: Supports row-level locking with hints like ROWLOCK, and uses lock escalation strategies depending on system load.&lt;/p&gt;

&lt;p&gt;PostgreSQL: Uses Multi-Version Concurrency Control(MVCC) but also supports row-level locks via SELECT FOR UPDATE.&lt;/p&gt;

&lt;p&gt;MySQL (InnoDB): Implements row-level locking for transactional consistency.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Non-SQL Databases
&lt;/h2&gt;

&lt;p&gt;MongoDB: Initially used global locks but now supports document-level locking, which is conceptually similar to row-level locking.&lt;/p&gt;

&lt;p&gt;Cassandra: Uses lightweight transactions and Paxos protocol to achieve row-level consistency in distributed setups.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. NewSQL Databases
&lt;/h2&gt;

&lt;p&gt;CockroachDB and Google Spanner: Offer SQL-like interfaces with distributed row-level locking or MVCC for high scalability and consistency.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Lock Escalation&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Lock escalation is the process of converting many fine-grained locks for example row-level locks into fewer coarse-grained locks e.g.table-level locks to reduce system overhead. SQL Server automatically manages lock escalation based on the number of locks and system resources&lt;/p&gt;

&lt;h2&gt;
  
  
  Benefits
&lt;/h2&gt;

&lt;p&gt;Increased Concurrency: Multiple transactions can access different rows of the same table simultaneously.&lt;/p&gt;

&lt;p&gt;Reduced Contention: Minimizes the chances of blocking and deadlocks by locking only the necessary rows.&lt;/p&gt;

&lt;h2&gt;
  
  
  Considerations
&lt;/h2&gt;

&lt;p&gt;Lock Escalation: Be aware of lock escalation, which can convert row-level locks to table-level locks if too many row-level locks are acquired&lt;/p&gt;

&lt;p&gt;Performance Overhead: Managing a large number of row-level locks can increase system overhead&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Row-level locking in SQL Server helps the system run faster and smoother by letting it control access to one row at a time. When you understand how it works, you can make your apps more efficient and able to handle more users at once.&lt;/p&gt;

</description>
      <category>sql</category>
      <category>architecture</category>
      <category>performance</category>
      <category>database</category>
    </item>
    <item>
      <title>Is Excel Still Relevant in the Era of Power BI and Python?</title>
      <dc:creator>Lilllian Wanjala Chengwa</dc:creator>
      <pubDate>Fri, 03 Oct 2025 08:20:21 +0000</pubDate>
      <link>https://dev.to/chengwalillian/is-excel-still-relevant-in-the-era-of-power-bi-and-python-n3k</link>
      <guid>https://dev.to/chengwalillian/is-excel-still-relevant-in-the-era-of-power-bi-and-python-n3k</guid>
      <description>&lt;h2&gt;
  
  
  Yes, Excel is still highly relevant in the era of Power BI and Python, but its role has evolved.
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Universal and Accessible&lt;br&gt;
The vast majority of business professionals in business have access to Excel and know how to use it at some level.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;It is often the default tool for quick analysis, budgeting,    financial modeling, and reporting.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Simple to use ,even for users without technical know-how.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Useful for quick checks and data cleaning.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Deep Integration in Business Workflows&lt;br&gt;
Excel is deeply embedded in finance, accounting, logistics, and other traditional business domains. Many ERP systems and reporting tools export data directly to Excel formats.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
    <item>
      <title>Key concepts of a schema</title>
      <dc:creator>Lilllian Wanjala Chengwa</dc:creator>
      <pubDate>Tue, 23 Sep 2025 11:15:35 +0000</pubDate>
      <link>https://dev.to/chengwalillian/key-concepts-of-a-schema-36f7</link>
      <guid>https://dev.to/chengwalillian/key-concepts-of-a-schema-36f7</guid>
      <description>&lt;h1&gt;
  
  
  Introduction
&lt;/h1&gt;

&lt;p&gt;Schemas are the blueprint of a database.&lt;/p&gt;

&lt;h2&gt;
  
  
  Types of Schemas
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Snowflake Schema&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Star Schema&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
  </channel>
</rss>
