Viewing 9 posts - 1 through 9 (of 9 total)
I did something similar. I made a persisted calculated field in the staging table that held the hash value. Then the CPU for hash calculation would get hidden by the...
January 7, 2019 at 9:01 am
So I had a weird setup.
September 26, 2018 at 9:55 am
andrew_c_worth@yahoo.co.uk (9/30/2015)
Dealing with the problem when it comes may well be a case of "Not my Problem", but someone will have to fix it. Software often ends up being used...
September 30, 2015 at 9:07 am
If you are doing single email look ups, I don't think anyone doubts the hash lookup can give you a reduction in logical I/O for slight increase in disk space,...
September 29, 2015 at 2:01 pm
You need to be very careful with your data types. If you have a variable that is varchar and a variable that is nvarchar, they make different hashes. ...
September 24, 2015 at 9:30 am
I guess it is possible that I misunderstood what SQL server is doing with the keyhash values stored in the index pages. It is certainly hashing the strings and...
September 24, 2015 at 8:23 am
roger.plowman (9/24/2015)
Given SQL Server is all about efficiency I'd be interested in seeing a performance breakdown between the Checksum() and index seek versions.
I managed a database with > 10 Million...
September 24, 2015 at 7:26 am
It is not hard to create email addresses where Checksums overlap.
if checksum('ks@gmail.com') = checksum('nc@gmail.com')
print 'Checksum function is weak'
If you really want to do something like this, I'd recommend hashbytes:
if convert(bigint,hashbytes('md5','ks@gmail.com'))...
September 24, 2015 at 6:50 am
I have a similar challenge.
I have 40 servers.
Each server has a [dbadb] database.
Each database has a view named v_DatabaseFiles that shows information on the database files & mountpoint...
August 24, 2015 at 2:16 pm
Viewing 9 posts - 1 through 9 (of 9 total)