Telegram RegisterThe public register of Telegram
Telegram profile photo for تعلم قواعد بيانات SQL Database

Channel

تعلم قواعد بيانات SQL Database

@sql_asp_project

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,792subscribers

+9 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001831557555
TypeChannel
Username@sql_asp_project
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/sql_asp_project

Growth

1,7831,7921,787.58 August 2026 — 1,783 subscribers8 August 2026 — 1,784 subscribers14 August 2026 — 1,788 subscribers17 August 2026 — 1,792 subscribers8 August 202617 August 2026
4 measurements spanning 9 days, net +9. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,782–1,793 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 20:371,792+4
14 Aug 2026, 21:281,788+4
8 Aug 2026, 19:261,784+1
8 Aug 2026, 11:471,783first reading

Engagement

20 posts held, back to 5 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 16 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 2 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 5 July 2026 to 16 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

16 Jul 2026, 13:31 UTC223 viewsread 8 August 2026

🎉 إجابة تحدي 14 هل كانت إجابتك صحيحة؟ 👀 SUM = 1000 AVG = 200 MAX = 300 MIN = 100 إذا كانت إجابتك صحيحة... اكتب في التعليقات: 🔥 تمت المهمة

16 Jul 2026, 07:52 UTC230 viewsread 8 August 2026

❓ سؤال لو كنت مدير شركة... أي معلومة تعتبرها أهم؟ A️⃣ إجمالي المبيعات B️⃣ متوسط قيمة الطلب C️⃣ أكبر طلب ولماذا؟

16 Jul 2026, 07:52 UTC218 viewsread 8 August 2026

الكود SELECT SUM(OrderAmount) AS TotalSales, AVG(OrderAmount) AS AverageSales, MAX(OrderAmount) AS HighestOrder, MIN(OrderAmount) AS LowestOrder FROM Orders; 💡 النتيجة Total Average Max Min 1250 250 450 80 🔥التحدي إذا كانت قيم الطلبات هي: 100 250 300 150 200 بدون تشغيل SQL... م

15 Jul 2026, 09:04 UTC186 views1 reactionsread 8 August 2026
File

📌 Lesson 14 | كيف يحسب النظام المجموع والمتوسط؟ عد أن تعلمنا GROUP BY... طلب منك مدير المبيعات تقريرًا يحتوي على: ✅ إجمالي المبيعات. ✅ متوسط قيمة الطلب. ✅ أكبر طلب. ✅ أصغر طلب. هل سنحسبها يدويًا؟ 🤔 طبعًا لا... SQL يوفر لنا دوال جاهزة. اليوم سنتعرف على: ✔️ SUM() ✔️ AVG() ✔️ MAX() ✔️ MIN()

1

15 Jul 2026, 07:54 UTC173 viewsread 8 August 2026

🚀 ممتاز... الآن أصبحنا نعرف: كم طلبًا قام به كل عميل؟ باستخدام: GROUP BY + COUNT لكن مدير المبيعات لم يكتفِ 😅 قال: 💰 لا أريد عدد الطلبات... أريد إجمالي قيمة الطلبات لكل عميل! ثم سأل: 📊 ما متوسط قيمة الطلب؟ 🔥 ما أكبر طلب؟ 🔥 وما أصغر طلب؟ هنا COUNT وحدها لن تكفي... الدرس القادم: Lesson 14 — Aggregate Functions SUM AVG MIN MAX 💬 سؤال قبل الدرس: إذا كان لدى عميل طلبان: 100$ + 250$ ما الدالة التي تتوقع أن نستخدمها لل

15 Jul 2026, 07:45 UTC121 viewsread 8 August 2026

تحدي اليوم — أقوى قليلًا 🏆 تحدي Lesson 13 لدينا جدول Orders: 101 → Customer 1 102 → Customer 1 103 → Customer 2 104 → Customer 3 105 → Customer 3 106 → Customer 3 107 → Customer 3 ونفذنا: SELECT CustomerID, COUNT(*) AS OrderCount FROM Orders GROUP BY CustomerID; ❓ ما النتيجة؟ اكتبها بهذا الشكل: Customer 1 = ? Customer 2 = ? Customer 3 = ? 🚫 ممنوع تشغيل SQL فكر أولًا كمطور تقارير 👨‍💻 💬 اكتب النتيجة في التعلي

15 Jul 2026, 07:44 UTC106 viewsread 8 August 2026

🤔 سؤال سريع | GROUP BY لدينا الطلبات التالية: Customer 1 → Order 101 Customer 1 → Order 102 Customer 2 → Order 103 Customer 2 → Order 104 Customer 2 → Order 105 بعد تنفيذ: GROUP BY CustomerID مع: COUNT(*) ما النتيجة؟ A️⃣ Customer 1 = 2 | Customer 2 = 3 B️⃣ Customer 1 = 1 | Customer 2 = 1 C️⃣ سيظهر 5 عملاء 💬 اكتب فقط A أو B أو C ثم اشرح السبب بجملة قصيرة 👇

15 Jul 2026, 07:43 UTC113 viewsread 8 August 2026

الكود الجاهز SELECT CustomerID, COUNT(*) AS OrderCount FROM Orders GROUP BY CustomerID ORDER BY OrderCount DESC; شرح سريع CustomerID نريد تقريرًا لكل عميل. COUNT(*) نحسب عدد الصفوف، أي عدد الطلبات. GROUP BY CustomerID نجمع طلبات كل عميل معًا. ORDER BY OrderCount DESC نعرض الأكثر طلبًا أولًا.

15 Jul 2026, 07:43 UTC124 viewsread 8 August 2026

الشرح المختصر للدرس لدينا جدول Orders: OrderID | CustomerID -------------------- 101 | 1 102 | 1 103 | 2 104 | 2 105 | 2 106 | 3 لو سأل المدير: كم طلبًا نفذ كل عميل؟ نحن لا نريد عرض 6 صفوف. نريد تقريرًا: CustomerID | OrderCount ----------------------- 1 | 2 2 | 3 3 | 1 هنا تعمل GROUP BY. هي تجمع الصفوف التي لها نفس CustomerID في مجموعة واحدة، ثم نستخدم COUNT() لحساب

10 Jul 2026, 22:03 UTC231 viewsread 8 August 2026

https://t.me/sql_asp_project شارك الرابط لكي يستفيد غيرك

9 Jul 2026, 05:01 UTC230 viewsread 8 August 2026
Photo

🔥 Lesson 13 | الآن تبدأ التقارير الحقيقية! تخيل أن جدول Orders يحتوي على 10,000 طلب... ومدير المبيعات سألك: ❓ كم طلبًا قام به كل عميل؟ هل ستعدّ الطلبات يدويًا؟ 😅 هنا نحتاج إلى: 🚀 GROUP BY فهي تحول آلاف الصفوف إلى مجموعات مفيدة للتقارير. مثلاً: Customer 1 → 5 Orders Customer 2 → 12 Orders Customer 3 → 3 Orders 💬 قبل مشاهدة الشرح: برأيك، هل GROUP BY تحذف الصفوف؟ أم تجمعها منطقيًا داخل مجموعات؟ 🤔 اكتب توقعك 👇 #SQLServer

Showing the 12 most recent of 20 posts we hold for @sql_asp_project. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 1,397,444 of 1,548,671entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 17 August 2026 — this entry's latest reading, not the date you are reading this.

“تعلم قواعد بيانات SQL Database” (@sql_asp_project), 1,792 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/sql_asp_project.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.