Comments
-
I agree that "grouping "similar" statements as one" is a great idea. I am going to paraphrase a quote from mandevil (Aug 24, 2016 10:51 AM, Historically Associate Queries): Recommendation: You can create a report that will look for specific SQLtext (some identifying pattern) that will pull back all of the hashes that match…
-
I would vote YES for this... but it depends on how it is implemented. We have a weekly process now that captures all of the recommended missing indexes (as well as "unused" indexes), which we aggregate to review which indexes get the highest "impact/occurrences". As with any SQL modification, a good knowledge of the data…
-
With a few modifications (add ignite.CONSW_1 "D", or "date" field), that query was just what I was looking for! Thanks!
-
Yes.... I found it also. I was getting errors on the plans / SQL queries which have dynamic variables and temp tables.
-
Looks like this query does the trick for SQL Server: Custom Report - Top SQL for Database User
-
Thanks for all of the replies/research! Sorry if my original request was misleading, but for this query, SQL Login = DB user = database user. What we need specifically is something similar to what is displayed on the "DB Users" tab, but • Filtered by a specific DB User. • Filtered by date range. • Ability to sum the total,…
-
> Now to the mapping: > If CONO_1 shows your dbnames, that is unexpected unless you name your databases after your OS users... Well, here is a partial result from the CONO_1 table. I know the SQL Users are in the Repository somewhere, as the "DB Users" tab in DPA looks fine.... hopefully we are talking about the same…
-
I have a task to try and quantify SQL server usage by specific users (customers). I was hoping this query was part of the solution, but the procedure (and the tables I have in my DPA instance, 9.1.x) appear to have a disconnect? Or am I just missing that this procedure is suppose to do? I know the data is in there…
