Viewing 15 posts - 2,296 through 2,310 (of 59,067 total)
I have a grand appreciation for anyone that steps up to the plate with an article.
Shifting gears to the subject at hand, this is an old method that was written...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2022 at 5:52 pm
And you should see what happens when you drop the table! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2022 at 5:23 am
Sorry Jeff.
I have been working with open query trying to get the values I need for my Insert into Staging Table. The query I have is returning some of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2022 at 9:57 pm
Jeff Moden wrote:Heh... I've been having issues with caffeine absorption lately. 😀
Too much ? Or not enough ?
Both, actually. Too much in the morning and too little in afternoon/evening, and...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2022 at 5:16 pm
Gosh, Bruin... how do you expect anyone to help with such little information?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2022 at 5:14 pm
I don't know about CyberArk but I would hope that getting a Password for an SQL Service Account couldn't actually be done in such an easy...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2022 at 2:20 am
I don't know the data well enough to say with conviction, but there has to be some criteria that you could use in an open query, other than a join,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2022 at 2:17 am
Heh... I've been having issues with caffeine absorption lately. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2022 at 2:10 am
Guys... the OP doesn't know which domains contain a "B" ahead of time. He was just explaining the desired results for the test data he provided. Or, at least, that's...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2022 at 1:50 am
Scratched the answer that was here... I didn't read the post correctly.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2022 at 1:38 am
The source table has 2 billion but not all records are chosen since it does a lookup ql.Tag_ID = sd.tagid
Any example of a script to do it in batches...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2022 at 1:31 am
Heh... you're the one touting the handle of "sqlguru". You should be teaching us how you fixed the issue. 😀
If you want help with a performance issue, we need more...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2022 at 1:24 am
No problem Jeff. Were it not for Coffee, I would never have survived the 20 years in the Navy!
I only did 8 1/2 in the Navy... Silent Service on...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2022 at 7:58 pm
Yeah... I just made that realization. Like I said in my edit of my previous post, the low level alarms for caffeine have sounded. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2022 at 7:21 pm
Have you tried running the queries with a hint to force the use of the legacy cardinality estimator?
Also... when you migrated the data to the new server, did indexes get...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2022 at 7:14 pm
Viewing 15 posts - 2,296 through 2,310 (of 59,067 total)