Viewing 15 posts - 4,636 through 4,650 (of 59,069 total)
p.s. If there's a DISTINCT or a GROUP BY that you're using like a DISTINCT, you really need to fix that. Really. And identifying the "core" data and using "Divide'n'Conquer"...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2021 at 2:38 am
You say "On some occasions, again all under the same execution plan, poor performance occurs " but the execution plans you posted aren't even close to being the same.
The culprit...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2021 at 2:36 am
AND, looking a bit closer, my code doesn't work correctly using the following data but the mod to pietlinden's code does, so use his code with the mod.
Here's the code...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2021 at 1:28 am
Looking a bit closer at the code, there' may be a fly in the ointment of pietlinden's code. Give the following a run and see.
[EDIT] I DISCOVERED THE CODE...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2021 at 1:04 am
Hi Phil,
Thanks for the reply.
The create/ insert would be as follows:
CREATE TABLE CustomerPolicies
(
[Mobile] NVARCHAR(20),
[WorkTelephone] NVARCHAR(20),
[HomeTelephone] NVARCHAR(20),
[FirstName] NVARCHAR(30),
[LastName] NVARCHAR(30),
[PolicyNumber] INT
)
INSERT INTO CustomerPolicies VALUES ('07972234564', 'N/A', 'N/A', 'Jon',...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2021 at 12:40 am
It's all Steve Jones. His idea. His execution. He deserves all the credit.
Not to mention being the prime driver of this whole site! +1 Billion to Steve!
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2021 at 12:16 am
Did any of those solutions help you or is there something else that you need help with on this problem?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2021 at 12:12 am
BWAAAA-HAAAA-HAAAA!!! I've found that "Penalty of Death" will sometimes work! 😀
I agree with Ant-Green's statement. All of our data is encrypted and that means everything and not just SQL Server...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2021 at 12:08 am
@jeff - while concat_ws deals well with nulls on this case it could also cause a collision on a case where one row has null vs one with ''...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2021 at 11:53 pm
P.S. I will also be presenting on the topic of Module Signing at the upcoming PASS Data Community Summit 2021: Module Signing: Use Certificates to...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2021 at 10:50 pm
Interesting. Thank you for taking the time to post the feedback.
Out of curiosity, when is the last time the SQL Server Service was restarted?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2021 at 10:36 pm
Steve,
I'm pretty sure that most folks will recommend against the use of the Lightweight Pooling option for most things. The reason I mentioned it was to make sure it wasn't...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2021 at 12:39 am
I agree with Brian. The code you posted doesn't even contain the "product_month" column and so I also wonder if you have the correct code posted or if you've just...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2021 at 11:17 pm
It could be a settings difference between VS and SSIS. For example, VS could be using connections that use one type of setting for ANSI NULLs and SSIS could be...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2021 at 10:27 pm
Been there and done that. Totally understood.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2021 at 4:58 pm
Viewing 15 posts - 4,636 through 4,650 (of 59,069 total)