Viewing 15 posts - 1,831 through 1,845 (of 59,067 total)
Right - but only the checksum column is keyed. With the number of collisions in checksum I would think you would hit a point of maximum entropy in index...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2023 at 12:50 am
I am skeptical that pre-fragmenting the index to 20% fragmentation with the 80% fill-factor is preferable to a relatively small amount of fragmentation that would result from changes to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2023 at 5:20 pm
You'll find that logical fragmentation just doesn't matter that much. Since you lowered the FILL FACTOR as you would for a Random GUID (which the BINARY CHECKSUM resembles in nature),...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2023 at 3:02 pm
This is the code which is creating the problem (bridgid is bigint ,remaks is varchar(250) status smallint) in both the tables mentioned below. INSERT INTO KKR (BridgID,Remarks,Status) SELECT DISTINCT...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2023 at 2:53 pm
I did some experiments with BINARY_CHECKSUM and I think that'll do for me and for my needs, it's good enough and simple to implement.
Also, if that solution works for...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2023 at 2:34 pm
I did some experiments with BINARY_CHECKSUM and I think that'll do for me and for my needs, it's good enough and simple to implement.
That's not going to help you...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2023 at 2:28 pm
Thank you very much. The "MAX" worked.
Awesome. Now, check the MAX(LEN() of the column so you can right-size it. It may still need to be a MAX but maybe...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2023 at 12:08 am
1)it is my stored procedure.
2) I debuged my sp and it stated running properly. and after that it was also running properly with same params.
but after sometimes it showed...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2023 at 10:26 pm
Trying to get different perspectives! May be I am looking at the things might not be the right. Getting awareness from wise people will definitely make me think...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2023 at 10:20 pm
Sounds like a prelude to spam.
Glad to see I wasn't the only one to think that. I subscribed to this thread yesterday to see if the other shoe drops.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2023 at 5:26 pm
And, just to be sure, my initial post didn't cite your response. It was meant more for the op. I'll explicitly state that next time.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2023 at 2:08 am
I know there was no mention of a normal time/attendance table.. that's why I'm mentioning it now. 😉 The overall process should keep track of all time by project/rate and...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2023 at 2:05 am
Jeff Moden wrote:I'm kinda curious why anyone thinks that a separate overtime table is needed at all.
Well it can't go in the Employee table.
Heh... Ya think? 😀
Why is there a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2023 at 1:53 am
At first blush, it would appear that the memo field of the file has at least one line in the file where the text of the memo is wider than...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2023 at 1:20 am
I'm kinda curious why anyone thinks that a separate overtime table is needed at all.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2023 at 1:13 am
Viewing 15 posts - 1,831 through 1,845 (of 59,067 total)