>This is IMHO not true. The simple reason for this is that once you have a proc which is used by multiple apps, you can't >hange it if it needs a new parameter/different type/updated resultset, because it will break a lot of apps, and perhaps these >aren't written in-house. So what do you do? You add a new one. After a couple of years, how do you think your db will look like?
The same is applicable for mehods that are called from multiple applications ! And if you develop COM applications, it's worst, believe me ! For sure, it's more performant to manipulate and filter data in the database management server instead of getting a big set of data and doing this in the application. The same is for data modification and insertion : you can have a set of data provided by the user that affects more than 1 table. What is more performant between executing multiple queries from the application or doing this on the server side ? And what about data validation that requires to interrogate other tables ? Please, think anything else than DataSet and DataAdapter, or anything else that is generating dynamic SQL behind. Think SQL. And it's a big sacrifice to develop applications in the mind of DBMS indepency. The reality is all DBMS are different and they all have features that can be very usefull. Take time to study them. In the case of an application that needs to be compatible with two or more DBMS, think to encapsulate the interraction between the application and DBMSs into a class. We are programmer, are we not ? =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
