Viewing 15 posts - 91 through 105 (of 134 total)
One problem does stand out in the snippet -- use of most functions in WHERE clauses or JOINS prevent sargability (ability to use indexes)
WHERE ABS(T2.CALL_PRICE -...
December 24, 2021 at 4:22 pm
the issue is not the sql itself but the whole combination - your system is likely constrained in memory and was unable to produce a plan for the full...
December 24, 2021 at 4:17 pm
As was communicated in a previous post, we don't know the definitions of the CTEs your referencing. Without DDL for all underlying tables/views, and the entire query, there is...
December 24, 2021 at 4:16 pm
I ran each CTE and I think I found the problem. It is this one:
SELECT
T2.UNDERLYING_SYMBOL,
T2.QUOTE_DATE,
T2.STRIKE,
T2.CALL_PRICE,
T2.PUT_PRICE
FROMNEAR_TERM_OPTIONS_CTE AS T2
INNER JOIN
(
SELECT
T1.UNDERLYING_SYMBOL,
...
December 24, 2021 at 4:56 am
I MAY be mistaken on this, but I think that an i9 is a desktop processor not a server processor. Generally, you would want to have SQL Server running...
December 19, 2021 at 8:38 pm
I have seen some websites that rank i9 quite high. Glen's site doesn't mention any i9 processors. Only Xeon. is there any particular reason why i9 are not mentioned?
December 18, 2021 at 10:28 pm
Hi everyone
Thanks for the replies. If I include the execution plan then does the query come with it automatically or do I have to add the query separately?
Thank you
December 14, 2021 at 5:16 pm
the concern I have is that if it takes 15 seconds to process a 600 row table then what it is going to look like when it has to process...
December 14, 2021 at 5:05 am
i fixed the problem
i changed the original column datatype from smallint to int and now the error is gone.
thank you everyone!
December 13, 2021 at 8:07 pm
I modified the query so i look at part piece by piece. the problem is with calculation
1.0 / (T1.NEAR_TERM_STRIKE * T1.NEAR_TERM_STRIKE)
the values for NEAR_TERM_STRIKE range from about 1000 to 3000.
I...
December 13, 2021 at 7:59 pm
this suggestion does work
SELECT CAST(0.0000005328 AS NUMERIC(18,18)) FROM TIME_CTE
it produces:
0.000000532800000000
not sure why it doesn't work in my CTE posted.
December 13, 2021 at 7:49 pm
I completely understand. I have posted sample code.
December 13, 2021 at 7:47 pm
thanks for the reply.
here is the code:
The column NEAR_TERM_STRIKE contains integers.
Even after putting the cast command I still get the same error. There is no other column in the query...
December 13, 2021 at 7:46 pm
it worked. thank you!!
December 4, 2021 at 5:51 pm
Thank you everyone. this is very helpful
November 26, 2021 at 10:24 pm
Viewing 15 posts - 91 through 105 (of 134 total)