November 22, 2017 at 9:51 am
PrettyMegaDBA - Wednesday, November 22, 2017 9:23 AMGrant Fritchey - Wednesday, November 22, 2017 9:19 AMYow!
I feel your pain. I'll try to get a moment to look at the plan, but, I'd say in addition to the code changes I suggested, you need to focus on clustered indexes first. The plan is probably a bit of a waste of time at the moment with no indexes on the tables. It's going to be all scans.
Thanks so much!
I agree with Grant. A proper clustered index will help you a lot and will change the plan immensely. To give you an idea on how indexes could affect a query, here's one example (totally unrelated) showing how a process went from over a day to approximately one minute. http://www.sqlservercentral.com/articles/set-based+loop/127670/
November 22, 2017 at 3:50 pm
drew.allen - Wednesday, November 22, 2017 8:25 AMJeff Moden - Wednesday, November 22, 2017 8:20 AMPrettyMegaDBA - Wednesday, November 22, 2017 8:16 AMThank you all for your responses. All have been very helpful. And forgive me, I lost my formatting somewhere between copy & paste, I will ensure its formatted better in the future. I will take the comments into consideration and see if that helps.PMD
The formatting thing has been a problem ever since they "improved" the forum software. :angry:
You can't blame this one on the forum software. The code was not included in the proper SQL Code tags.
Drew
If you look at the code that was included in the tags, it still sucks. 😉 I'm also thinking that it wasn't copied and pasted directly from SSMS either.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2017 at 3:55 pm
Jeff Moden - Wednesday, November 22, 2017 3:50 PMdrew.allen - Wednesday, November 22, 2017 8:25 AMJeff Moden - Wednesday, November 22, 2017 8:20 AMThe formatting thing has been a problem ever since they "improved" the forum software. :angry:
You can't blame this one on the forum software. The code was not included in the proper SQL Code tags.
Drew
If you look at the code that was included in the tags, it still sucks. 😉 I'm also thinking that it wasn't copied and pasted directly from SSMS either.
I try NOT to copy/paste directly from SSMS, it adds extra lines that I can't seem to remove. I go to a text editor, UltraEdit, first. Even then I have had issues with the SQL Code block at times.
November 23, 2017 at 10:44 am
Lynn Pettis - Wednesday, November 22, 2017 3:55 PMJeff Moden - Wednesday, November 22, 2017 3:50 PMdrew.allen - Wednesday, November 22, 2017 8:25 AMJeff Moden - Wednesday, November 22, 2017 8:20 AMThe formatting thing has been a problem ever since they "improved" the forum software. :angry:
You can't blame this one on the forum software. The code was not included in the proper SQL Code tags.
Drew
If you look at the code that was included in the tags, it still sucks. 😉 I'm also thinking that it wasn't copied and pasted directly from SSMS either.
I try NOT to copy/paste directly from SSMS, it adds extra lines that I can't seem to remove. I go to a text editor, UltraEdit, first. Even then I have had issues with the SQL Code block at times.
It didn't use to be that way just before this latest change. They spent a good amount of time making sure that the code windows worked great and they did. All that is gone now and it doesn't matter whether you use IE, FireFox, Chrome, or whatever Web Browser you prefer.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply