There are many benefits to using ORM Tools, but they are not a replacement for Stored Procedures ORM Tools are a replacement for the manual process of defining and writing data and/or business classes. It saves the developers time and effort by letting them worry about what data to get instead of how to get the data (amongst other things) Additionally, stored procedures are usable (and sometimes recommended) alongside ORM Tools.
There are many benefits to using ORM Tools, but they are not a replacement for Stored Procedures. ORM Tools are a replacement for the manual process of defining and writing data and/or business classes. It saves the developers time and effort by letting them worry about what data to get instead of how to get the data (amongst other things).
Additionally, stored procedures are usable (and sometimes recommended) alongside ORM Tools.
– Seekav Mar 8 at 17:20 Honestly Stored Procedures should be used whenever possible. They provide you with more flexibility (IE: small changes to SQL without needing to recompile/install/deploy the application). I find that if I'm making a utility application (something that might only get used twice a year) then I do not bother with making stored procedures though.
– Tony Abrams Mar 8 at 17:29.
ORM tool is not a replacement of stored procedure. It reduce your task to write class that mapped with database and realationship among those class. It also check the validatoin on data you don't need to do manual stuff for this.
Stored procedure can also be used with ORM tool alongside.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.