d8a93e67-210e-45aa-819e-b551aa345b8c #12485
Replies: 27 comments 1 reply
-
|
Really practical approach to database cost optimization, I like how it connects performance with real ROI, not just tech improvements |
Beta Was this translation helpful? Give feedback.
-
|
It's always nice to optimized and save some money. |
Beta Was this translation helpful? Give feedback.
-
|
Make it work |
Beta Was this translation helpful? Give feedback.
-
|
Figuring out expensive queries can be tricky, nice to see options for tools to help us with that ! |
Beta Was this translation helpful? Give feedback.
-
|
Implementing telemetry from day 1 will ensure your decisions can be data-driven... optimisation and thorough data pair well. |
Beta Was this translation helpful? Give feedback.
-
|
There are two things that are the most important after just delivering the application.
|
Beta Was this translation helpful? Give feedback.
-
|
This is a great rule! I have only really looked at DB optimisations from a speed perspective. Considering cost is a massive motivator for a lot of businesses - These tools are super useful. Would be nice if azure just showed these stats out of the box 🤑 |
Beta Was this translation helpful? Give feedback.
-
|
I have only optimized queries in regard to speed before. WISdom seems like a great tool to optimize the pricing of the cost as well. |
Beta Was this translation helpful? Give feedback.
-
|
Not a dev but making anything faster, cheaper or more optimised seems like a no brainer |
Beta Was this translation helpful? Give feedback.
-
|
Nothing regarding query costs, but query performance for sure. Working on old stored procedures, I found a lot of nested cursors iterating through table rows (super expensive). This was the cause of many deadlocks within our database, and resolving it, I imagine, decreased costs significantly too. Would've been good to have WISdom to show the FINops on that. |
Beta Was this translation helpful? Give feedback.
-
|
Can we get AI to do the audit? Take the SQL code an get Claude to optimise? |
Beta Was this translation helpful? Give feedback.
-
|
That's a solid general approach. Every cloud provider and exact stack have their own tools and tricks that make life easier when it comes to tracking down the costs. It's worth checking the best tool for your particular setup. With the widespread use of ORMs it is also worth including db operations review in a normal tech debt payback where practical. |
Beta Was this translation helpful? Give feedback.
-
|
It's great to have tools like these that make it easier to drill down and figure out which queries are the slowest That being said I think it's important to focus on this when performance becomes an issue, not beforehand. Premature optimisation is the root of all evil |
Beta Was this translation helpful? Give feedback.
-
|
Showing the cost benefits of database optimisations definitely make it easier for businesses to understand |
Beta Was this translation helpful? Give feedback.
-
|
It looks like a cool tool and I would give a try. I didn't like the ROI planner since you can punch in unrealistic numbers for a query. It would be better if you'd let the tool analyse the query, db, table structure it then comes up with a potential saving that translates into dollars. |
Beta Was this translation helpful? Give feedback.
-
|
As a SysAdmin... this is great! Cost optimisation is important, and showing ROI is a useful feature. |
Beta Was this translation helpful? Give feedback.
-
|
Pretty cool tool to help save money 🤩 |
Beta Was this translation helpful? Give feedback.
-
|
those are great tools to visualise the database spending and a good metric for optimization |
Beta Was this translation helpful? Give feedback.
-
|
Really useful reminder that performance tuning is now a cost conversation too. Seeing which queries drive CPU, IO, and execution frequency gives devs a much better place to start than random indexing. |
Beta Was this translation helpful? Give feedback.
-
|
It's awesome when Devs optimise there resource usage as this affects the costs in our tenant. |
Beta Was this translation helpful? Give feedback.
-
|
I love seeing the list of query by cost! Very useful tool |
Beta Was this translation helpful? Give feedback.
-
|
This is very useful rule for cloud native systems |
Beta Was this translation helpful? Give feedback.
-
|
It’s always better to keep the cost low, and using tools like WISdom is a good approach. It seems very easy to use. |
Beta Was this translation helpful? Give feedback.
-
|
Great rule! It provides excellent clarity on database spending, moving us from guesswork to data-driven cost control. |
Beta Was this translation helpful? Give feedback.
-
|
No war stories but i think its easy to miss these kind of things when developing - we use mock data, tables are mostly empty, and traffic is low. This is a great tool to look at every now and then (maybe at sprint reviews). Incorporating performance/load testing is also a good way to uncover potential issues before getting to prod. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting rule gents |
Beta Was this translation helpful? Give feedback.
-
|
For my clients, I’ve had a lot of success getting my specifications (that describe my query) to automatically output query tags. This gets outputted as OTEL as well… that way I know exactly which file in the codebase to optimise and how often particular queries are being used. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
d8a93e67-210e-45aa-819e-b551aa345b8c
Learn how to optimize Azure SQL and SQL Server costs by identifying expensive queries, prioritizing high-ROI fixes, and using FinOps tools to calculate potential savings.
https://www.ssw.com.au/rules/database-query-costops
Beta Was this translation helpful? Give feedback.
All reactions