October 18, 2016 at 3:47 pm
A question about Software application development and SQL database.
We are implementing .net applications that uses SQL server as backend databases.
When developing the applications what is the best approach, code driven, database driven, or business rule driven? Where should business rules implemented?
One .net developer asked a SQL DBA/developer does most of the things in stored procedures, also add calculated columns so that he can just simply display the fields on UI.
Is this a good way to do software development, or what is the best approach?
Thanks,
October 18, 2016 at 5:20 pm
A serious subject for debate but I've seen what happens if you don't do the database-first thing first. I strongly recommend database-design first. Everything else is easy after that. Do it any other way and you suffer for the life of the database. It takes a bit longer (but only a bit) up front but saves big $ and time afterwards.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 19, 2016 at 12:41 pm
A agree with Jeff. Unless it is relatively simple you should design your database objects and define the relations as it conforms to business rules but also considering what type of system this is (OLTP, Reporting, Analysis) and what type of transaction rate and how big the database will be.
Doing this properly can and will make your business logic simpler, reporting easier, give better concurrency and be easier to document. Not doing this properly is what causes 80% of the issues that end up turning a project into a nightmare.
The probability of survival is inversely proportional to the angle of arrival.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply