> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/sustainability-best-practices/backend/sql-optimization.md). # SQL optimization Efficient SQL optimization, particularly in the precise utilization of joins, carries significance within the framework of sustainable system design. Employing the correct joins can enhance database performance, leading to reduced resource consumption, minimized processing time, and ultimately, a more sustainable system. By crafting queries that make optimal use of joins, developers can avoid data redundancy, eliminate unnecessary processing, and ensure efficient data retrieval. This streamlined approach aligns seamlessly with sustainable design principles, where resource efficiency and reduced strain on infrastructure are vital for long-term system viability. A well-optimized **SQL** **schema** with appropriate joins contributes not only to faster response times and enhanced user experiences. But it also minimizes the system's energy requirements. Thus, investing in proper SQL optimization practices, specifically focusing on the judicious use of joins, is a pivotal step. A pivotal step towards creating a software ecosystem that operates harmoniously with the ideals of environmental preservation and resource efficiency. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.umbraco.com/sustainability-best-practices/backend/sql-optimization.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.