Уровень 0 · материалов: 6
В кластер входят документы, посвященные техническим методам повышения производительности и мониторингу работы СУБД, и не входят документы о безопасности доступа к данным или общем мониторинге веб-приложений.
Общие признаки: производительность БД, мониторинг состояния БД, оптимизация SQL-запросов, управление индексами и блокировками, инструменты анализа БД
Группа выше: Диагностика деградации производительности
Смысл: The main idea is to provide database administrators and developers with a set of ready-to-use SQL queries to monitor PostgreSQL's internal state, manage locks, optimize index usage, and handle database bloat to ensure optimal performance.
A practical collection of SQL queries for monitoring PostgreSQL performance, managing locks, and optimizing storage and indexing.
Смысл: The main idea is to introduce 'sp_WhoIsActive' as a more efficient, informative, and flexible alternative to built-in SQL Server monitoring tools for identifying active sessions and performance bottlenecks.
The author compares standard SQL Server monitoring tools and recommends the 'sp_WhoIsActive' stored procedure for detailed, real-time server activity analysis.
Смысл: The main idea is to introduce and demonstrate the MySQL profiling feature as a simple and effective way for developers to analyze and optimize the performance of their SQL queries.
The author explains how to use the MySQL profiling feature to track query execution time and identify performance bottlenecks.
Смысл: The main idea is that database performance in SQL Server is maintained by regularly addressing index fragmentation through automated scripts or tools that choose between reorganization and rebuilding based on the severity of the fragmentation.
A technical guide on automating MS SQL Server index defragmentation using T-SQL scripts and a recommendation for a free open-source management tool.
Смысл: The main idea is to optimize database interactions by replacing multiple individual queries inside loops with a few bulk queries, thereby reducing latency and improving application performance.
To improve performance, avoid placing SQL queries inside loops and instead use bulk fetching with the 'IN' operator to reduce the number of database round-trips.
Смысл: The main idea is to optimize the 'GetOrCreate' database pattern in multithreaded C# applications by minimizing lock duration and scope, transitioning from long-lived main transactions to short-lived independent transactions to increase throughput.
The author explores three ways to implement a thread-safe 'GetOrCreate' database operation, concluding that using short, independent transactions for insertion maximizes performance but sacrifices atomic rollback.