Viewing 15 posts - 3,151 through 3,165 (of 59,098 total)
MySQL functions --
DATE_SUB(CURDATE(), INTERVAL 7 DAY)-- won't be of much use on SQL Server 2019.
Yeah... that's just spam for an "Assignment writing" service to help people...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 2:55 pm
Here's the rendition I came up with. It produces the same answer as Phil's. The % of Batch in the Actual Execution Plan says that mine is 27% faster but...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 2:44 am
Ok... now that I've read the post that I missed, I've added 'P6' to the list of PartNumbers with all '2's for 3 entries to test.
--Add 'P6'...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 2:02 am
the goal mfrom asking question is to get result above without string aggreagte or comma separated suppose i have
p1 1,2,3
p2 2,2,2
both p1 and p2 both have same count and...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 1:49 am
I still want to know why the OP wants to avoid the STRING_AGGREGATE() function.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 12:20 am
I work with what I consider a large number of third party databases. I still troubleshoot poorly performing queries. I now have DBA acquaintances at those companies and they...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2022 at 11:46 pm
Hi Jeff,
Thanks for getting in touch.
I will take a look at the link, however I think I'm going to struggle as to where to apply the COLLATE clause
I can't...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2022 at 7:33 pm
the goal mfrom asking question is to get result above without string aggreagte or comma separated suppose i have p1 1,2,3 p2 2,2,2 both p1 and p2 both have...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2022 at 6:15 pm
I stand to be corrected, but the pattern appears to be as follows
...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2022 at 6:13 pm
If that's true, then you might have to apply the COLLATE clause. See the following search for more information.
https://duckduckgo.com/?q=COLLATE+(Transact-SQL)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2022 at 6:03 pm
Hello Community,
When I execute the attached code I get the following error:
Implicit conversion of varchar value to varchar cannot be performed because the collation of the value is unresolved...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2022 at 5:21 pm
I am sure that there is no process which is attempting sending multiple times.
Don't be so sure. We had a similar problem with a "wonderful" web service that someone...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2022 at 2:00 pm
Thanks for all the feedback everyone. Appreciated.
Me, I love tuning queries.
Yes Jeff, working on the new book. Chapter 20 right now, Graph data.
@Grant ,
Awesome... I don't know how you...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2022 at 1:43 pm
so, hypothetically, I am the boss. I used to be technical; but that was long time ago. I am responsible to the users for the performance of the application...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2022 at 1:36 pm
I'm in the same boat. Why would P4 have the same "unique" number as P3 and P5 have the same "unique" number as P2?? I'm just not seeing your "pattern"...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2022 at 1:23 pm
Viewing 15 posts - 3,151 through 3,165 (of 59,098 total)