Viewing 10 posts - 1 through 10 (of 10 total)
Before using MERGE in MS SQL Server, it would be good read this article as well. I'm not sure how many of the bugs mentioned there have been...
January 26, 2021 at 7:20 am
Thank you @jonfrisbee and the other contributors for this useful information all in one place. Adding your stored procedure to my "toolkit"!
Nice to see an article about real...
January 11, 2021 at 8:12 am
Aha! Great article, and I can immediately see a use case for having unique numbers even across different tables, where both tables get the number generated by the same sequence. e.g:
May 28, 2020 at 12:07 pm
There aren't 365 days in a year. Seeing that hard-coded constant in the code raised about seventeen code-smells in my mind
April 9, 2018 at 4:08 am
Check out schemazen - a free command line tool that scripts outs a whole SQL Server database. It places different object type into different folders, and scripts the database options...
April 6, 2018 at 4:22 am
Useful article, thank you!!
Thanks to the internet archive (Wayback Machine), we know that MS tried to implement "in-line scalar functions" which would not have had the cost mentioned...
June 2, 2017 at 5:20 am
CROSS APPLY has the advantage that the function is only called once for each possible value of the function parameters, rather than once for each row. Convert it to a...
October 28, 2014 at 8:22 am
For cadastral surveying (i.e. property / town / state / country boundaries) with corrected GPS readings, we regularly get less than 1cm error per kilometer, which is 0.001% error. Of...
September 26, 2014 at 11:04 am
Well for the real world it would be 1.60934 kilometers per mile
September 26, 2014 at 4:54 am
It might be good to put the radius of the earth as a constant at the top of the function (or initialised variable in SQL), so readers of...
September 26, 2014 at 4:53 am