Data Analytics
Perfect channel to learn Data Analytics Learn SQL, Python, Alteryx, Tableau, Power BI and many more For Promotions: @coderfun @love_data
Show more๐ Analytical overview of Telegram channel Data Analytics
Channel Data Analytics (@sqlspecialist) in the English language segment is an active participant. Currently, the community unites 109 631 subscribers, ranking 1 124 in the Technologies & Applications category and 2 395 in the India region.
๐ Audience metrics and dynamics
Since its creation on ะฝะตะฒัะดะพะผะพ, the project has demonstrated rapid growth, gathering an audience of 109 631 subscribers.
According to the latest data from 17 June, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by 689 over the last 30 days and by -19 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 3.31%. Within the first 24 hours after publication, content typically collects 1.51% reactions from the total number of subscribers.
- Post reach: On average, each post receives 3 624 views. Within the first day, a publication typically gains 1 658 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 7.
- Thematic interests: Content is focused on key topics such as row, sql, analytic, analyst, visualization.
๐ Description and content policy
The author describes the resource as a platform for expressing subjective opinions:
โPerfect channel to learn Data Analytics
Learn SQL, Python, Alteryx, Tableau, Power BI and many more
For Promotions: @coderfun @love_dataโ
Thanks to the high frequency of updates (latest data received on 18 June, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.
SELECT
name,
department,
salary,
DENSE_RANK() OVER (PARTITION BY department ORDER BY salary DESC) AS salary_rank
FROM employees;
I applied DENSE_RANK() window function partitioned by department and ordered by descending salary to assign ranks within each department. Unlike ROW_NUMBER(), DENSE_RANK() handles ties by assigning the same rank without gaps. This is ideal for leaderboards or performance analytics.
๐ง๐ถ๐ฝ ๐ณ๐ผ๐ฟ ๐ฆ๐ค๐ ๐๐ผ๐ฏ ๐ฆ๐ฒ๐ฒ๐ธ๐ฒ๐ฟ๐:
Master window function differences (ROW_NUMBER vs RANK vs DENSE_RANK)โthey're interview staples for deduping, paging, and top-N queries!
React with โค๏ธ for moreSELECT
department,
MAX(salary) AS second_highest_salary
FROM (
SELECT
department,
salary,
ROW_NUMBER() OVER (PARTITION BY department ORDER BY salary DESC) as rn
FROM employees
) ranked
WHERE rn = 2
GROUP BY department;
I used a subquery with ROW_NUMBER() window function partitioned by department to rank salaries in descending order within each department. The outer query then filters for rank 2 (second highest) and groups to get distinct departments. This demonstrates mastery of window functions, which are essential for advanced analytics and ranking problems.
๐ง๐ถ๐ฝ ๐ณ๐ผ๐ฟ ๐ฆ๐ค๐ ๐๐ผ๐ฏ ๐ฆ๐ฒ๐ฒ๐ธ๐ฒ๐ฟ๐:
Window functions like ROW_NUMBER(), RANK(), and DENSE_RANK() unlock complex ranking and analyticsโpractice them daily to ace behavioral and technical rounds!
React with โค๏ธ for moreCREATE DATABASE db_name;
- USE db_name;
2. Tables
- Create Table: CREATE TABLE table_name (col1 datatype, col2 datatype);
- Drop Table: DROP TABLE table_name;
- Alter Table: ALTER TABLE table_name ADD column_name datatype;
3. Insert Data
- INSERT INTO table_name (col1, col2) VALUES (val1, val2);
4. Select Queries
- Basic Select: SELECT * FROM table_name;
- Select Specific Columns: SELECT col1, col2 FROM table_name;
- Select with Condition: SELECT * FROM table_name WHERE condition;
5. Update Data
- UPDATE table_name SET col1 = value1 WHERE condition;
6. Delete Data
- DELETE FROM table_name WHERE condition;
7. Joins
- Inner Join: SELECT * FROM table1 INNER JOIN table2 ON table1.col = table2.col;
- Left Join: SELECT * FROM table1 LEFT JOIN table2 ON table1.col = table2.col;
- Right Join: SELECT * FROM table1 RIGHT JOIN table2 ON table1.col = table2.col;
8. Aggregations
- Count: SELECT COUNT(*) FROM table_name;
- Sum: SELECT SUM(col) FROM table_name;
- Group By: SELECT col, COUNT(*) FROM table_name GROUP BY col;
9. Sorting & Limiting
- Order By: SELECT * FROM table_name ORDER BY col ASC|DESC;
- Limit Results: SELECT * FROM table_name LIMIT n;
10. Indexes
- Create Index: CREATE INDEX idx_name ON table_name (col);
- Drop Index: DROP INDEX idx_name;
11. Subqueries
- SELECT * FROM table_name WHERE col IN (SELECT col FROM other_table);
12. Views
- Create View: CREATE VIEW view_name AS SELECT * FROM table_name;
- Drop View: DROP VIEW view_name;SELECT
category,
SUM(quantity * unit_price) AS total_revenue
FROM customer_orders
GROUP BY category;
4. How would you find repeat customers?
SELECT
customer_id,
COUNT(order_id) AS order_count,
SUM(quantity * unit_price) AS total_spent
FROM customer_orders
GROUP BY customer_id
HAVING COUNT(order_id) > 1;
โข Customers with order_count > 1 are repeat buyers.
5. How would you detect โtop customersโ?
โข Define โtopโ by total_spent or average order value:
โ SUM(revenue) / COUNT(orders)
โข Use Power BI/Excel to sort descending and highlight top 10%.
6. What would an outlier analysis look like?
โข Compute min, max, average, standard deviation of revenue per order.
โข Flag orders where:
โ revenue > average + 2 * standard_deviation
โข Check if such orders are errors or real big deals (e.g., enterprise purchase).
7. How would you report monthโonโmonth growth?
โข In SQL/Power BI:
โ Group by YEAR(order_date) and MONTH(order_date)
โ Compute revenue per month
โ Then calculate:
โช MoM % = (CurrentMonthRevenue โ PreviousMonthRevenue) / PreviousMonthRevenue
8. How would you turn this into a dashboard?
โข Page 1 โ Overview: Cards for total revenue, total orders, AOV.
โข Page 2 โ Trends: Line chart for MoM revenue, bar chart for category split.
โข Page 3 โ Customers: Table for top 10 customers and repeat customers.
9. How would you handle dirty data (nulls, duplicates)?
โข Preโcheck:
โ COUNT(*) vs COUNT(customer_id) to spot missing customers.
โข Clean:
โ Drop or impute missing critical fields.
โ Remove duplicate orders using DISTINCT or ROW_NUMBER().
10. How would you explain your findings to a nonโtech manager?
โข Use simple language + visuals:
โ โOur top product category is Electronics, contributing X% of revenue.โ
โ โN top customers account for M% of total sales.โ
โข Avoid formulas; focus on business impact: retention, profitability, growth.
Double Tap โค๏ธ For More!
Available now! Telegram Research 2025 โ the year's key insights 
