Black Falcon Software Releases SQL Helper 4.5
July 8, 2015 Leave a comment
One would be right in questioning as to why we would need a new basic data-access-layer when we have so many alternatives currently.
Black Falcon Software has always promoted the simplest and easiest way to implement a code-base that is elegantly coded. However, such a definition of software development increasingly seems to mean using languages with arcane syntax along with tools that increase and not decrease the overall complexity of an application. Much of this has been encouraged by the latest marketing hype that defines the 21st century as a time that has developed new business requirements in need of new development tools.
With the crossing of the millenniums this is a great tool for vendors to sell an entirely new host of wares that in reality offer very little in benefit to application developers and the business organizations they work for. What one can do with the latest, shiny software tools can still be done quite well and efficiently with the mature products that have been in use for years.
Despite the possible disbelief of the younger generations of software professionals, business institutions are still the same corrupt, narcissistic entities they were when they were first designed and incorporated in the 17th century. In fact, just to raise a few eyebrows here, all of the business organizations we have either worked for or are currently working in were designed as institutional swindles. The business corporation was promoted as a complete con. It was so successful in this vein that England outlawed such entities for over 200 years. Yes, there were still businesses in this time but they were all privately owned whereby any consequences as to their failures and\or inability to generate revenue were the sole responsibility of the “business owners”. Corporations and even many privately held companies today were designed to put any such failures on others and the monies they invested.
In any event, this slight historical distraction was to demonstrate that nothing has changed in terms as to how any of these organizations operate simply as a result of going from the year 1999 to 2000. All businesses want to simply take your money and how they do so has only changed in methodology and style. Their requirements for doing so have remained as they always were; get something done in the fastest way possible and who cares about quality.
What has changed though is the level of complexity that is seemingly being fostered on the Information Technology field by using processing exceptions to standard software development as the rule instead of the rare exception. What does this mean?
How many times have you read an article or been to a seminar where the author or lecturer is presenting a coding methodology that is prefaced with the statement, “Let’s say you want to be able to do this…”
That is what a processing exception is defined by; the idea that somehow something may come up that will allow you to use a “new” feature in your favorite language. Guess what…
What is being presented here can just as easily be done in the way you would have had to do it without the new coding feature. And your application will still work just fine.
This is exactly how the push for the use of Object Relational Mapping (ORM) layers was promoted and suddenly the efficiency of simply using an ADO.NET data access layer went out the window. The promise was that you didn’t have to interface directly with your database engine and you didn’t have to use SQL. Instead, you got to use an additional abstraction called LINQ or something similar. The result was that now you added a weighty layer of abstraction to your application and you had to learn an often confusing new syntax. Did your application work any better? No. Did it work any faster? Absolutely not! However, you were now convinced that anything was possible with your application’s database access when you would most likely never need any such extensive capability.
To drive these points home a little further, a quick look at the short posting at the following link should convince you of why using a straight-forward data-access-layer is a better bet for application development… https://n0tw0rthy.wordpress.com/2011/05/28/orms-hidden-cost/
Black Falcon Software’s new SQL Helper 4.5 software has been completely re-written along with a new and much cleaner Test-Client tool that has been designed with WPF. You get all of the source-code as well as complete documentation as to how the data-access-layer and its components can be used.
You can download the software (“Sql Server DAL (4.5)”.) at the following link…
Enjoy and get back to writing data access as it should be written…