The Proximity project is coming along. I have successfully loaded a large family tree from a GEDCOM file and a very large set of pedigrees downloaded from Ancestry DNA using DNAGedcom.com. Name, place, and date parsers are working reasonably well, although there is considerable room for improvement. I have been doing a great deal of refactoring as I discover, bit by bit, how to usefully apply a relational database system to solving difficult genealogical problems.
Update (3/28/17): As a simple workaround, I added a string split UDF that does the same thing (only much more slowly). If I need to compile the DB project, I replace the intrinsic function with the UDF in the two places it is called. Otherwise I switch back to the intrinsic. It’s annoying, but what else is a person to do? (I noticed this comment on Connect: “Some fixes have been added to SSDT regarding STRING_SPLIT. If you continue to experience the issue, please try out the next SSDT release.” I will indeed check it out.) [The fix is supposed to be in a “preview” release, which I have not installed. I will test it when the production release comes out.]
I happened to use the new (SQL Server 2016) STRING_SPLIT function in a table-valued function that I wrote the other day. When I went to sync the database to my SSDT database project, however, the project would no longer compile.
119 SQL Code Smells.
Why Local Variables are Bad for Tuning Stored ProceduresBrent Ozar Unlimited®.
Cursor-Killing: Retrieving Recently Modified Data – SQLServerCentral.
TSQL User-Defined Functions: Ten Questions You Were Too Shy To Ask.
The LookupCTE trick described here is pretty slick. These days I find myself working with large databases where these things really matter and I found this post quite interesting. Improving Query Performance by using correct Search Arguments – SQLServerCentral.
Clever. I don’t think I had ever heard of EXCEPT. Using EXCEPT to Determine Row Differences – SQLServerCentral.
Here we go with developers again. I wonder if the ones that go around creating this particular kind of mess are also the ones that tend to flunk the index/performance quiz? Fixing Cache Bloat Problems With Guide Plans and Forced Parameterization.
Well at least I “passed” (4 out of 5). Hint: read the questions CAREFULLY. Most SQL users flunk performance test | ITworld.