Viewing 15 posts - 3,121 through 3,135 (of 59,067 total)
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
Do you have an example where the master data doesn't equal the imported data? If so, please don't post it as a graphic... post it as readily consumable data. One...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2022 at 10:19 pm
Other than my "fun" response above, the reason why I study it all is because of two things.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2022 at 6:00 pm
Do NOT let users have direct access to xp_CmdShell... Write a stored procedure that uses xp_CmdShell with the correct proxy and EXECUTE AS OWNER in the proc.
NEVER EVER let users...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2022 at 4:59 am
Why bother? It's funny... there must be a disturbance in the force because I've been asking myself the same questions a whole lot lately. For me, it all boils down...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2022 at 1:36 am
The error always occurs in the Excel Data Source at the start of the data flow. Only ever there, but which file it fails on is random. Often it...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2022 at 5:01 pm
That's incredibly kind feedback, Zidar. Thank you very much. I truly appreciate it and, like any author, feedback like yours and the others on this thread helps keep us going.
Shifting...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2022 at 3:36 pm
Viewing 15 posts - 3,121 through 3,135 (of 59,067 total)