🔥 Today’s win: Set operations UNION | INTERSECT | EXCEPT Finally understand how to combine results from multiple queries like a real query composer 🧩 #SQLQuery #DataEngineering #100DaysOfCode

Please like, comment, and subscriber to get database related tips & tricks on daily basis. #dbms #DatabaseEngineer #sqldeveloper #sqldatabase #sqldba #DBA #DBAProgram #madesimplemssql #SQLDBA #Analyticss #programming #coding #backend #sqlquery #sqltraining #datasecurity #data

Please like, comment, and subscriber to get database related tips & tricks on daily basis. #dbms #DatabaseEngineer #sqldeveloper #sqldatabase #sqldba #DBA #DBAProgram #madesimplemssql #SQLDBA #Analyticss #programming #coding #backend #sqlquery #sqltraining #datasecurity #data

Day 10 of the @hertechtrail #HTTDataChallenge was to retrieve customer names in alphabetical order using SQL query. SELECT name (retrieves only the name column) FROM accounts (your customer names are in the accounts table) ORDER BY & ASC (sorts in ascending order ) #SQLQuery

8 days in spreadsheets was a good run, but I've officially moved the stack to SQL Managing an orders tables scale requires more than just filters. It requires data integrity and speed. Scaling up✨💫👌🏼 #HTTDataChallengeDay9 #SQL #FMCG #DataAnalytics #SQLQuery

I’m early today😂🤭 Day 9 of the @hertechtrail #HTTDataChallenge task is to retrieve all column from any specific table I used the commands SELECT * FROM region; Result = 4 rows and 2 columns SELECT * FROM accounts; Result = 351 rows and 7 columns #SQLQuery #SQLBasics

One thing worth knowing: SqlQuery<T> works for unmapped types, but if you need to query your actual mapped entities with raw SQL, use FromSql instead. They look similar but behave differently - FromSql participates in change tracking and respects your entity configuration, while SqlQuery<T> is purely for projection into arbitrary types.

Day 6 of Learning SQL Combining of Data (contd) Types of Joins No join – Returning Data from two tables without combining them, frame 1 shows an example on it. Inner Join – It returns only the matching rows from both tables, frame 2 shows an example on it. Left join- It returns all the rows from left and only the matching rows from the right table, frame 2 also shows an example on it . Right Join – It returns all the rows from the right table and only the matching rows from the left table frame 3 shows an example on it. Full Join - It returns all the rows for both tables, frame 3 also shows an example on it. #dataengineering #sqlquery

sqlQuery redd.it/1rd82vn

I'm feeling the same way RStudio ... allbookings = data.frame(sqlQuery(conn, q1)) Error: memory exhausted

1- Dapper => Use ef-core SqlQuery<T> 2- Serilog => MS.Ext.Logging OpenTelemetry 3- Dapr => Aspire 4- TestContainers => Aspire 5- GraphQL => OData

With EF8, you can compose raw SQL queries and LINQ. The SqlQuery method returns an IQueryable, meaning you can call any LINQ method. The resulting SQL will be a nested query, which isn't ideal. However, the database can optimize this. What do you think about this EF feature?

/* High-level logic never lies */ bool is_active = false; int records_affected = 0; SQLCONN db = sql_connect("SQLSERVER_CORE"); SQLQUERY q = sql_prepare( "SELECT trace_id, event_time " "FROM audit_log " "WHERE card_state = 'INACTIVE'" ); -->

Hello SQL fam 👋, I’m currently deep into my data analyst job preparation and practicing as many real-world SQL and Python questions as I can. Here’s one I worked on today 👇 Problem Statement :- Products table has three columns namely ProductID, Product and Category. Write a SQL query to interchange the ProductIDs for Products as shown in the desired output. #sql #sqlquery #dataanalytics #dataanalyst #learning #jobprep #sqlpractice #tech #LearningInPublic

𝟭𝟬 𝗦𝘁𝗲𝗽𝘀 𝘁𝗼 𝗠𝗮𝗸𝗲 𝗬𝗼𝘂𝗿 𝗘𝗙 𝗖𝗼𝗿𝗲 𝗤𝘂𝗲𝗿𝗶𝗲𝘀 𝟭𝟬𝘅 𝗙𝗮𝘀𝘁𝗲𝗿 Most .NET developers don't realize this: EF doesn't limit your query performance — it's limited by how you use it. If your API feels slow, your dashboards lag, or queries take seconds to load, you're likely missing these simple optimizations 👇 𝟭. 𝗔𝗱𝗱 𝗗𝗮𝘁𝗮𝗯𝗮𝘀𝗲 𝗜𝗻𝗱𝗲𝘅𝗲𝘀 EF Core doesn't automatically create indexes. Add them manually for columns used in WHERE, JOIN, and ORDER BY. → Use .HasIndex() in your entity configuration. → Create a manageable number of indexes 𝟮. 𝗢𝗽𝘁𝗶𝗺𝗶𝘇𝗲 𝗤𝘂𝗲𝗿𝘆 𝗣𝗿𝗼𝗷𝗲𝗰𝘁𝗶𝗼𝗻𝘀 Stop fetching full entities when you only need a few fields. → Use .Select() to return only what's required. → Smaller payloads = faster materialization and less memory usage. 𝟯. 𝗨𝘀𝗲 𝗔𝘀𝗡𝗼𝗧𝗿𝗮𝗰𝗸𝗶𝗻𝗴 𝗳𝗼𝗿 𝗥𝗲𝗮𝗱-𝗢𝗻𝗹𝘆 𝗤𝘂𝗲𝗿𝗶𝗲𝘀 Tracked entities consume memory and CPU. → Add .AsNoTracking() for read-only queries. → Or set global QueryTrackingBehavior .NoTracking for read-only DbContexts. 𝟰. 𝗟𝗶𝗺𝗶𝘁 𝗡𝘂𝗺𝗯𝗲𝗿 𝗼𝗳 𝗡𝗮𝘃𝗶𝗴𝗮𝘁𝗶𝗼𝗻𝘀 Too many .Include() calls can cause N 1 queries or massive joins. → Include only what's necessary. → Filter includes where possible 𝟱. 𝗔𝘃𝗼𝗶𝗱 𝗟𝗮𝗿𝗴𝗲 𝗜𝗡 / 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝘀 𝗙𝗶𝗹𝘁𝗲𝗿𝘀 Huge Contains() lists generate slow SQL IN clauses. → Fetch IDs in smaller batches. → Or store filter data in a temporary table and join it instead. 𝟲. 𝗨𝘀𝗲 𝗣𝗮𝗴𝗶𝗻𝗮𝘁𝗶𝗼𝗻 𝗳𝗼𝗿 𝗟𝗮𝗿𝗴𝗲 𝗗𝗮𝘁𝗮𝘀𝗲𝘁𝘀 Don't load thousands of records into memory. → Use .Skip() and .Take() for offset-based pagination. → Or switch to cursor-based pagination — it's faster and index-friendly. 𝟳. 𝗨𝘀𝗲 𝗖𝗼𝗺𝗽𝗶𝗹𝗲𝗱 𝗤𝘂𝗲𝗿𝗶𝗲𝘀 Frequent queries can be precompiled. → Cache LINQ-to-SQL translation with EF .CompileQuery(). → It's perfect for queries used in loops or called often. 𝟴. 𝗨𝘀𝗲 𝗦𝗽𝗹𝗶𝘁𝗤𝘂𝗲𝗿𝘆 𝘁𝗼 𝗔𝘃𝗼𝗶𝗱 𝗖𝗮𝗿𝘁𝗲𝘀𝗶𝗮𝗻 𝗘𝘅𝗽𝗹𝗼𝘀𝗶𝗼𝗻 Multiple .Include() joins can cause data duplication. → Add .AsSplitQuery() to break large joins into smaller queries. → Ideal for complex relationships (Author → Books → Publisher). 𝟵. 𝗨𝘀𝗲 𝗥𝗮𝘄 𝗦𝗤𝗟 𝗳𝗼𝗿 𝗖𝗼𝗺𝗽𝗹𝗲𝘅 𝗢𝗽𝗲𝗿𝗮𝘁𝗶𝗼𝗻𝘀 Sometimes SQL just wins. → For complex filtering, locking, or joins — use .FromSqlRaw() or .SqlQuery<T>(). → You get full control over the query plan. 𝟭𝟬. 𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗲 𝗖𝗮𝗰𝗵𝗶𝗻𝗴 Don't hit the database for frequently accessed data. → Use in-memory cache or Redis. → For .NET 9 , try HybridCache — it solves cache stampede issues. 📌 Bonus Tip: Measure before optimizing. Use BenchmarkDotNet, SQL Profiler, or query plans to confirm your bottlenecks. 👉 Join 𝟭𝟳,𝟬𝟬𝟬 software engineers reading the best EF Core blogs on the market: antondevtips.com/blog?catego… —— ♻️ Repost to help others optimize EF Core ➕ Follow me ( @AntonMartyniuk ) to improve your .NET Skills

I dove into the data to uncover some key insights: 🔹 Identified the count of female users from Canada. 🔹Discovered the most common occupation among all users. 🔹Listed the 5 oldest users in the system. #DataAnalytics #SQLQuery #UserDemographics #LearningInPublic

💥 EF Core vs SQL Injection Cuando ejecutas SQL directo desde Entity Framework Core, la seguridad depende totalmente del método que elijas 😬 ✅ Primer ejemplo — Seguro y recomendado 🧩 Interpolación segura (SqlQuery) EF Core convierte automáticamente tus variables en parámetros SQL seguros. 🛡️ Esto evita inyecciones y protege tu base de datos sin esfuerzo. ⚙️ Ideal para la mayoría de los escenarios donde necesitas ejecutar SQL personalizado. ✅ Segundo ejemplo — Correcto con precaución 💬 Uso de SqlQueryRaw con parámetros explícitos EF Core ejecuta SQL “en crudo”, pero tú defines los parámetros de forma segura (@param). 🔒 Así previenes inyecciones sin perder flexibilidad. 💡 Perfecto cuando necesitas control total sobre la consulta. ❌ Tercer ejemplo — Inseguro y peligroso 🧨 Concatenar valores directamente en SQL Esto abre la puerta a ataques de SQL Injection, permitiendo que un atacante modifique la consulta para acceder o eliminar datos. 🚫 Nunca construyas tu SQL con strings concatenados. 🔥 Este error es más común de lo que crees… ¡y el más costoso! 🔐 Conclusión: ✨ Usa SqlQuery siempre que sea posible. ⚙️ Si usas SqlQueryRaw, nunca concatene strings: pásalos como parámetros. 💡 Recuerda: la seguridad no es opcional, ¡es parte del diseño! Tu base de datos (y tu equipo de seguridad) te lo agradecerán 😉 #EntityFrameworkCore #dotnet #Security #SQLInjection #CleanCode #NetUniversity #CSharp #Developers #CodingTips

Will adding comments to Teradata tables impress my tables or just confuse them more? Source: devhubby.com/thread/how-to-a… #TechTips #SQLQuery #DatabaseTips #DataAdministration #exist #comments

Day 7 of #LeetCode SQL 50 👨‍💻 Problem: Customers Who Never Order #100DaysOfCode #SQLChallenge #LearnInPublic #CodeNewbie #DevJourney #DataWithSQL #TechTwitter #DatabaseDesign #SQLQuery #WomenWhoCode #DataScience #DataAnalytics #SQLforDevelopers #DailySQL

Hi Folks Which condition returns rows where manager_id is empty? . . #sql #sqlquery #dataanalyst #follow @bkarishma360 for me more....