Viewing 15 posts - 826 through 840 (of 59,070 total)
Not aimed at the author but aimed at the whole concept... Let's look at the first example prompt in the article...
You are an SQL Server database developer. Assume you...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2024 at 5:01 am
Heh... let's look at the first paragraph in the article...
It's a good idea to learn more about different technologies. I've been amazed throughout my career, and even now as...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2024 at 5:46 am
Not enough info... we're just guessing from descriptions. Please see the article at the 2nd link in my signature line below for what to post for these types of performance...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2024 at 5:30 am
Possible solution to the original question...
Given the original example data...
Create Table #Payments (ID int, Comment Text)
INSERT INTO #payments values (1, '65607 Processed via? DISC Last 4 digits...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2024 at 4:51 am
In this case I would start splitting the comment based on a space.
check "Tally OH! An Improved SQL 8K “CSV Splitter” Function"
and process the spliter results...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2024 at 4:17 am
Phil Parkin will tell you that I'm not a big fan of SSIS or most of the any other 4 letter words in SQL Server.
That not withstanding and with the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2024 at 4:10 pm
Rule number 1: Claims of efficiency and/or performance MUST be accompanied by demonstrable code to prove it.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2024 at 12:51 am
Third, the clustered index does store data in physical order on pages. The pagse/extents could get out of order, which is fragmentation, but that doesn't change the physical nature...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2024 at 8:22 pm
And I dont think its going to be fast with that many records - was really just hoping that there might be a faster way that I wasn't thinking...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2024 at 6:59 pm
Jeff
the query is the slow part of a larger process.its not being posted to a screen - query is part of universe of claims process that needs to look...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2024 at 6:57 pm
Hi Steve,
Thanks for getting back. I was given this table and figured out that this field a varchar(4000) was the field with the start and end dates times. I...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2024 at 4:09 am
It returns over 22m records in about 5 minutes.
According to your query, you're returning 22 million rows to the screen...
Question: What makes you think that's going to be fast? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2024 at 4:05 am
That's great but without the book, the uncommented code you posted doesn't explain at all what the code is supposed to be teaching.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2024 at 3:54 am
A serious word of caution on the use of PAGE compression... If you're into doing any index maintenance, PAGE compression will nearly double the time and CPU it takes. You...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2024 at 3:39 am
It's just a select from 3 tables, and 2 of them are with left join. For aggregations, I would have done it on SQL Server side. Now I...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2023 at 12:29 am
Viewing 15 posts - 826 through 840 (of 59,070 total)