Viewing 15 posts - 1,606 through 1,620 (of 59,067 total)
That would happen if you did not have ord.Amount wrapped in the aggregate SUM function.
It should work w/ the query listed.
It can't... there's no ORDER_ID column in the Vendor...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2023 at 6:41 pm
You are correct. Each 7000 byte + the ID row occupies 1 page.
On my box, I'm always getting 2 reads more than the number of leaf level pages regardless of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2023 at 6:30 pm
It'll be interesting to see what kind of Execution Plan is built from all that. The use of DISTINCT also suggests that you may have at least 1 many-to-many return...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2023 at 5:06 pm
In the following, you have an underscore in the code that does not exist in the TBL_Vendor table.
on vnd.ORDER_ID = ord.ID
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2023 at 4:56 pm
Lordy. My apologies. I didn't look at the "record layout" for sys.dm_tran_active_transactions (from your query you posted)... The bloody database_transaction_begin_time column in that DMV is returned, by the system, as...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2023 at 3:44 pm
Thanks, ran into someone that didn't know you could do this in one statement.
That's the main reason I really liked the question. I've run into a whole lot of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 3, 2023 at 2:42 pm
@Sridevi kakolu,
Thanks for the reply and the referenced material . I was worked with this option for many PTO tasks, but what I am looking for is , a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 3, 2023 at 2:07 pm
Heh... Like I tell people, I don't hate computers... I hate the people that write the code and the people that don't test it properly.
And you don't even know if...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 3, 2023 at 1:20 am
Nice question, Steve!
--Jeff Moden
Change is inevitable... Change for the better is not.
April 3, 2023 at 1:14 am
Like I said, glad to "meet" you.
The reference you provided is very helpful but it doesn't tell the OP how to find content like you did for the first thing...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 3, 2023 at 12:06 am
Why does creating and inserting data into a table with insert into cause blocking but inserting into an existing table not cause blocking?
Someone like Paul White could answer that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2023 at 9:32 pm
The tran log I/O seems really high to me, as does query store. Without having more esoteric knowledge of the system, I'm hesitant to make any judgement on that.
I will...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2023 at 7:40 pm
I was shocked to learn that this table still exists in SQL Server, and nobody is talking about it ^^. It seems to be around since the 80s as...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2023 at 6:00 pm
Nothing like shifting gears but, whatever. It's also not always the "better" way. "It Depends".
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2023 at 5:50 pm
Ah... never mind... I found the source.
Consider telling the OP the search you did to find this documentation so that they may help themselves in the future. I believe it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2023 at 1:48 pm
Viewing 15 posts - 1,606 through 1,620 (of 59,067 total)