1c-query-optimization

Optimize complex 1C queries using temporary tables and proper joins.

40|11|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Desko77/claude-code-skills-1c --skill 1c-query-optimization-desko77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-query-optimization
Source: https://github.com/Desko77/claude-code-skills-1c/tree/main/skills/1c-query-optimization
Command: npx skills add https://github.com/Desko77/claude-code-skills-1c --skill 1c-query-optimization-desko77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Advanced patterns for 1C query optimization to improve performance by reducing costly joins, subqueries, and data processing overhead.

Core Features & Use Cases

  • Apply advanced patterns such as using temporary tables, proper joins over subqueries, and avoiding aggregation in subqueries to boost performance.
  • Follow ITS Query Optimization Standards for consistent, scalable query design.
  • Use cases include complex multi-step data processing, large datasets, and heavy reporting workflows in 1C environments.

Quick Start

Analyze a given 1C query and propose immediate optimization steps using temporary tables, joins, and avoidance of subqueries.

Frequently Asked Questions about 1c-query-optimization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I optimize 1C queries with complex joins and subqueries?

Optimize 1C queries by replacing costly subqueries with temporary tables and proper joins. This reduces processing overhead and improves performance in data-intensive 1C environments handling large datasets.

Why does my 1C report run slowly on large datasets?

1C reports run slowly on large datasets due to costly joins, subqueries, and data processing overhead. Refactoring queries to use temporary tables and avoiding aggregation in subqueries boosts performance significantly.

What are the ITS standards for 1C query optimization?

ITS query optimization standards guide consistent, scalable query design in 1C. They require using temporary tables, applying proper joins, and avoiding inefficient subqueries to ensure scalable performance.

Does this 1C query optimization approach work with EDT and MCP validation?

Yes, this 1C query optimization approach is applicable to data-intensive projects involving EDT/MCP validation. It helps refactor complex multi-step data processing and heavy reporting workflows to improve performance.

When should I use temporary tables instead of subqueries in 1C?

Use temporary tables in 1C instead of subqueries when dealing with complex multi-step data processing or large datasets. Temporary tables reduce costly joins and aggregation overhead, significantly boosting query performance.