Viewing 15 posts - 3,691 through 3,705 (of 59,087 total)
Although mostly about memory, the following article has some pretty good stuff about examining things when you have long running queries.
https://www.erikdarlingdata.com/sql-server/does-my-sql-server-need-more-memory/
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2022 at 4:56 pm
Ar you saying that you still need real live "running totals" in the output? If so, my question, again, would be WHY? What problem would those help you solve?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2022 at 3:52 pm
Hi Experts,
I have several more than 60+ Dates and I need to know which is last valid date for a particular record ?
All the timers are extracted in a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2022 at 3:51 pm
With large tables, it's not likely that statistics are up to date (Frederico hinted at this in his post). What are you doing to keep statistics up to date (especially...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2022 at 3:30 pm
Easy now... in this case, the OP has pretty much stated what they want to do. The problem with the HAVING is that it becomes difficult to select the rest...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2022 at 2:42 am
This is supposed multi-selection question, isn't it? If so, radio buttons aren't going to work here.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2022 at 2:33 am
Ok... so the first and very important step is to "know thy enemy". With that, we have to know the "gazintas" for both tables. Run the following query one each...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 3, 2022 at 9:52 pm
I'm thinking that's still going to result in a massive accidental cross join I previously spoke of for the rows where all 3 of the join criteria are blank or...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 3, 2022 at 5:40 pm
Total agreement with all of you. Thanks for the comments.
Thanks for the article and your comments, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 3, 2022 at 5:37 pm
This does the trick for me.
WITH cteByDB AS
(--==== Preaggregate that data including a grand total using ROLLUP and marking that total row with GROUPING_ID.
...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 3, 2022 at 4:21 am
All those NULLs and Blanks that you're joining on? Yeah... guess what they're doing? MASSIVE accidental CROSS JOIN which is more politely called "many-too-many" join just on those alone.
Second, are...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 3, 2022 at 1:45 am
I love having a choice for all the reasons that both sides have stated both as a presenter and as an attendee. It's the best of both worlds.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 3, 2022 at 12:46 am
Thank you. It appears that Full Text Indexes have been available on Azure since 2015 so that's not the issue. The probable issue is that all software on Azure is...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 3, 2022 at 12:09 am
The use of the SUM(OVER) Windowing function should do it for you.
I also have to ask... why to you need a "running total" for this? Are you actually looking for...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2022 at 10:23 pm
I don't know much about the language used in SSRS but why wouldn't you just find the position of the colon, add 1 to that, and use that as the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2022 at 10:19 pm
Viewing 15 posts - 3,691 through 3,705 (of 59,087 total)