Activity overview
Latest activity by Matthew_Sontum
The reason I feel it deserves to be prioritized is that it causes existing working code not to work. As a first step in editing code (code I did not write myself) I run it through the SQL Prompt Formatter. I can no longer trust that the code will work after expanding wildcards, so I cannot use this feature at all until the issue is resolved. And yes, this has already caused an issue. I commit the code in source control after running it through the formatter, so that formatting changes can be reviewed separately from functional changes in code. If the SQL Prompt formatter is making functional changes this methodology breaks down. / comments
The reason I feel it deserves to be prioritized is that it causes existing working code not to work. As a first step in editing code (code I did not write myself) I run it through the SQL Prompt Fo...
It's still an issue (I posted about it earlier). If you format (and expand wildcards) : WITH CTE1 AS ( SELECT *, a+b as ab FROM #TempTable), CTE2 AS ( SELECT *, c+d as cd FROM CTE1) SELECT * FROM CTE2 It becomes:
WITH CTE1 AS (SELECT *, a + b AS ab FROM #TempTable),
CTE2 AS (SELECT CTE1.ab, c + d AS cd FROM CTE1)
SELECT CTE2.ab, CTE2.cd FROM CTE2; The other * columns from #TempTable aren't returned in the final output
/ comments
It's still an issue (I posted about it earlier). If you format (and expand wildcards) :WITH CTE1 AS (SELECT *, a+b as ab FROM #TempTable), CTE2 AS (SELECT *, c+d as cd FROM CTE1)SELECT * FROM CTE2I...
SQL Prompt incorrectly expanding *
This is an edge case, but it is reproducable. In some code that I ran the SQL Prompt formatter on recently there was a common table expression that referenced a temporary table, and then another co...
Thanks for the utils.GZipToString. I should be able to use this to build my own query. I am still hopeful that there is a feature built into the product that can do this, or will be in the future. / comments
Thanks for the utils.GZipToString. I should be able to use this to build my own query. I am still hopeful that there is a feature built into the product that can do this, or will be in the future.
Also, on a related note, how do you turn the _querytext column in data.Cluster_SqlServer_TopQueries_Instances into plain text? / comments
Also, on a related note, how do you turn the _querytext column in data.Cluster_SqlServer_TopQueries_Instances into plain text?
I am already aware of that method, and have used it in the past. That method works well when a particular query is already on my radar. What I'd like is more along the lines of a report that lists the top 10 queries and stored procedures whose average duration has increased over the last week. I don't want to click individually on each top 50 query I suspect may have gotten worse over time. And again, I am mainly concerned about relative performance, queries whose performance has slipped, not just the top 50 now. / comments
I am already aware of that method, and have used it in the past. That method works well when a particular query is already on my radar. What I'd like is more along the lines of a report that lists ...
How do you track performance of [top] SQL queries over time?
In preparation for changing the database compatibility level for our primary database to 2014, we would like to see which queries and stored procedures are performing poorly after the switch is mad...
Top 10 Objects / Stored Procedures?
Is there already a way to see the top 10 SQL objects in the main monitor pane? I can see a tab for top 10 queries and top 10 waits, but I would like to know the top 10 SQL objects (functions or sto...
How do you see the calling parameters / underlying stored procedure for a top SQL Query
I am new to using the Red Gate SQL Monitoring Tool. The main thing that I need to use it for is to determine the stored procedures in our system that are taking the longest to return (on average) a...
Unfortunately, every object in the database (1000+) has already been formatted with the format file that I sent you, with an earlier version of RedGate SQL Prompt 9.x that didn't have this error. Since the database is under source control it isn't a trivial matter to reformat, the original formatting took weeks and caused a lot of merge conflicts. Please pass this issue on to the RedGate SQL Prompt support team so that they can determine which version it started breaking in, why, and determine how to fix it. / comments
Unfortunately, every object in the database (1000+) has already been formatted with the format file that I sent you, with an earlier version of RedGate SQL Prompt 9.x that didn't have this error. S...