Viewing 15 posts - 4,201 through 4,215 (of 59,087 total)
When I run into problems like the one's you're having, I go back to the basics.
The first step is to get out of the dynamic SQL world and get some...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2021 at 4:36 pm
When I run into problems like the one's you're having, I go back to the basics.
The first step is to get out of the dynamic SQL world and get some...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2021 at 4:35 pm
When I run into problems like the one's you're having, I go back to the basics.
The first step is to get out of the dynamic SQL world and get some...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2021 at 4:35 pm
When I run into problems like the one's you're having, I go back to the basics.
The first step is to get out of the dynamic SQL world and get some...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2021 at 4:35 pm
See the following where Wayne Sheffield teaches the ropes on how to do this prior to having String_Agg() available.
https://www.sqlservercentral.com/articles/creating-a-comma-separated-list-sql-spackle
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2021 at 4:31 pm
Go look at the code itself. It getting hungup on something of yours might be an indication of something you've done seriously wrong to begin with.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2021 at 4:27 pm
When I run into problems like the one's you're having, I go back to the basics.
The first step is to get out of the dynamic SQL world and get some...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2021 at 4:21 pm
Heh... mine has started off with a bit of a "well that sucks" factor. Whole new time-keeping system where they want me to categorize virtually every aspect of what I...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2021 at 3:47 pm
How's everybody? Wishing a good 2022
Doing good, Jo. Thanks for asking.
Same to you and yours.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2021 at 3:35 pm
BUT even if you DO get it on your screen, there are a LOT of typos in it which makes it impossible to copy-paste into SSMS UNLESS...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2021 at 3:32 pm
You are selecting from [@IND_ORLS] & joining [@IND_RLS1], but there are no table-valued-parameters w/ those names and no table types of those names declared & populated in the procedure. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2021 at 3:32 pm
How i can resolve it
Thanks
Your findings don't appear to match your code where you say...
SET @Where = @Where + ' T0.U_DATE BETWEEN ''2021-03-01'' and ''2021-03-31'' '
I...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2021 at 2:16 am
So, do you see anything at all in the printed SQL that could be causing a problem? Like maybe in the FROM clause? and the JOIN table that follows that?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2021 at 1:23 am
Once you assign an alias to a table, that alias is the only valid way to reference that table. That's not a matter of preference or opinion. It's a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2021 at 12:36 am
There is no question in my mind that the form of updating an alias and having a FROM clause is easier in a lot of respects. I even said that...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 16, 2021 at 10:34 pm
Viewing 15 posts - 4,201 through 4,215 (of 59,087 total)