Update (2/26/17): It turns out that I did have uses for several of the GDAL 2.1 features, and there was a simple fix for the problem — switch to a different distribution. I tried the GIS Internals msi installer and everything worked the way it should.
I am developing a proof-of-concept for a genealogical database intended to support querying for various proximities including Generational relationships (traditional family tree) Proximity of events in time and space (geolocation) Genetic proximity (DNA matching via SNPs) …Continue reading →
Love this… This is nothing new but it’s still a fun idea. The problem: The vendor app we just purchased (and are told we must keep) requires the sa password. The vendor insists that sa is hard coded int… Source: SA Spoof | SQL Studies
Update (7/25/16): You should be fine with older versions of Report Server and SSMS 2016/Visual Studio 2015/SSDT, if you do these three things: Set the appropriate compatibility level for deployment (TargetServerVersion) in the report project properties. Build the report project before deploying (this may also catch some kinds of errors). …Continue reading →
It has been years since I tried selecting the RS 2012 option that automatically configures Report Server at installation time. I vaguely remembered that there was a good reason never to use it, but I felt like I needed reminding. And there was. …Continue reading →
The weirdness of SSRS dataset stored procedure metadata, explained at last! I have fought this battle in the past and won, eventually, but it sure is nice if you know the enemy. “Evil” is no exaggeration. Dealing with the Evil of FMTONLY from SSRS – SQLServerCentral.