Channel
@SQLFeathers
On this record: Growth · Engagement · What this channel posts · Posts · Telegram's recommendations · Cite this entry
5,324subscribers
+0 since we began measuring on 26 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001172362864 |
|---|---|
| Type | Channel |
| Username | @SQLFeathers |
| Description | A Big SQL Community - Channel for SQL Server Professionals or to help you to learn SQL. Write to Us ([email protected]) for SQL Support. |
| Created | Between 1 March 2018 and 21 August 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 September 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/SQLFeathers |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 01:22 | 5,324 | no change |
| 26 Sept 2026, 00:47 | 5,324 | first reading |
20 posts held, back to 21 August 2020 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 8 March 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 26 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Resource Waits: Lock Waits: waiting for a shared lock on a table - 'LCK_M_S' IO Waits: waiting for a page to be read from disk. 'PAGEIOLATCH_SH' Memory Waits: waiting for a semaphore to be released to access memory 'RESOURCE_SEMAPHORE' Queue Waits: CPU Waits: waiting for another process to complete. its work - 'CXPACKET' Memory Waits: waiting for an external memory allocation to be released. 'MEMORY_ALLOCATION_EX…
One of the MNC looking for following position Job Title: Product Architect Location : Kerala Trivandrum Primary Skill: C#,.Net,WebApi,jQuery,Java,SQL Year exp : 10+ Years Shoot your CV: [email protected]
SQL Feathers: Fatal error during installing SSMS or Vsts https://www.sqlfeathers.com/2021/07/fatal-error-during-installing-ssms-or.html
Multiple positions open for SQL BI (SSAS/SSRS) support Engineer at Microsoft India. Location Bangalore/Hyd Candidates having experience 5-12 years can be referred. Share your resume on [email protected]
Opportunity with an MNC in Infopark, Cochin We are Looking for Java Backend Developers having 3-8 Years of experience with Java/J2EE. We provide excellent opportunity to grow, learn and upgrade your skill sets by working with an international team Job Location: Kochi,Infopark,Kerala,India Requirement: Total experience of 3-8 Years with Java/JEE out of which at least 1 year in REST APIs using Spring/ Spring boot. …
https://t.me/SQLFeathers
https://www.mssqltips.com/sqlservertip/6993/power-bi-email-reports-power-automate-rls/?utm_source=dailynewsletter&utm_medium=email&utm_content=headline&utm_campaign=20211006
https://www.sqlfeathers.com/2014/04/rownumber-rank-denserank-ntile-in-sql.html?m=1
https://www.sqlfeathers.com/2021/07/fatal-error-during-installing-ssms-or.html?m=0
1.DevOps Architect 2.DevOps - Senior Engineer 3.DevOps Engineer 4.DevOps Infrastructure Senior Engineer 5.Linux Platform Architect 6.Android Application Lead 7.ADAS Architect 8.Infotainment Software Lead for Kanzi 9.Infotainment System Platform Architect 10.Python MicroServices Engineer/Lead 11.QT c++/QML 12.ML Engineer 13.Data Architect 14.Java Full Stack / Core Java 15.UI Technologies-Angular / Reacts 16.Cloud Tech…
https://www.sqlfeathers.com/2020/04/finding-blockinglocking-queries-in-sql.html?m=1
https://www.sqlfeathers.com/2018/05/sql-query-optimization-tips.html?m=1
Showing the 12 most recent of 20 posts we hold for @SQLFeathers. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Ms SQL Server” (@SQLFeathers), 5,324 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/SQLFeathers.
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.