Viewing 15 posts - 7,591 through 7,605 (of 59,091 total)
This is even more challenging in medical. If you are a blood lab and run a panel of tests, some of them greatly depend on the birth sex...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2020 at 1:03 am
Found the problem.... *sigh*
Our infrastructure team spun up a copy of our production environment, but forgot to update the firewall to prevent it from communicating outside itself. So it...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 6:59 pm
Did 'he' say whether this is a one-off requirement, or something which will need to run periodically?
I can't help in SSIS but I try to code "one-offs" such as...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 6:57 pm
A bit of a sidebar... I cannot agree with changing the ISO spec. People who make the change all want to be identified by the gender they've chosen and the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 6:51 pm
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
Viewing 15 posts - 7,591 through 7,605 (of 59,091 total)