Yes, performance will suffer under large load.
The database schema is a contract between the database developer and the
business tier/UI tier developers. It should not be changed without good
reason. Generisizing data access is not necessarily a bad idea, but I would
not do it on an app merely because you want to change data types without
having to alter DataSet formats, etc.
If you want flexibility in your sample apps or in applications that are used
to generate code or query databases, that is fine. These types of tools
generally end up with one person hitting the database at a time. Do not
genericize apps that need to scale.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"Islam Elkhayat" wrote:
I have created a class to use adp.FillSchema() method to generate Query
string & needed paramters on runtime and assign vlues for this paramters b4
calling the adp.update() method..
this give me the ability to change data types in the database without
editing my code as long as the paramters value is in the right format..
which mean i have to connect to my database 2 times or i could open it once
and excute fillschema & update methods then close the connection ...
So is this solution will work fine in large number of users requests??