Viewing 15 posts - 7,576 through 7,590 (of 59,072 total)
The XQuery is slow while executing in SSMS for first time.I am using SQL Server 2008 R2.
Heh... I know... big surprise there, right? 😀
The total time taken for...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 6:33 pm
Thanks Sue.
Yes Jeff, the same I have asked our management, they want all in zero cost. We are small 3 person team.
Heh... you're also a 150+ server team. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 6:01 pm
It's the insert and update that are locking the table.
You can ignore these locks by using the nolock hint:
select count(*)
from mytable with...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 5:58 pm
Ok... "Basic Sets". Let's do that. I don't have time just now to write the full solution (on my way to work, which also means that it's not fully tested)...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 2:48 pm
...
Heh... I wonder how many people actually got this question right without having to run the code?
Even I knew about quirky update and I'm only a lowly developer....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 1:10 pm
First, thank you for the article. I think that anyone that steps up to the plate to share their knowledge is ok in my book.
Shifiting gears, I'm a bit confused...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 12:27 pm
Heh... I wonder how many people actually got this question right without having to run the code?
I've been using a related technique to emulate STRING_AGG, so it wasn't...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 12:10 pm
I've done many of those tests myself... if you can get Minimal Logging to come into play, the inserting into a Clustered Index is MUCH faster than inserting into a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 11:54 am
From the post:
Not sure where this is useful or why it's there, but if anyone uses this, let us know.
If you yabingle "quirky update", you'll find examples of its...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 11:48 am
Interesting, but I'd be wary of using it. In a multi-row update, the result is pretty much undefined, unless all the rows are updated to the same value. And...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 11:45 am
@JeffModen:
There's a known issue with SET IDENTITY_INSERT ON... it forces full materialization of the data in TempDB and sorts it. ARCHIVE tables just don't need the IDENTITY PROPERTY on...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 2:18 am
Thanks! Would this work for whole db rather than individual table? How about Primary keys and clustered index?
You've got to be really careful about disabling any PK or UNIQUE...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 12:26 am
No... you still have the LSN problem.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 12:09 am
As a bit of a side bar, I'm always amazed when someone says they have a shedload of servers but no money to actually support them. It just doesn't make...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 12:07 am
>> your examples didn't have a join in - they were single table selects <<
If you've done a good job with your schema, then they will be a lot...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 9, 2020 at 11:25 pm
Viewing 15 posts - 7,576 through 7,590 (of 59,072 total)