Hi all,

I need to know if I have a prtitioned DB is it better to insert rows into the View or I should insert directly into the table that meet the constraints using execute statment, note that our system is inserting new rows each minute with too many records.

I'd say we need more data than this to answer the question.

Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee

I would say that the answer is it depends. It depends on how you are doing the update, what the front end is, etc. If you are using an updatable view to pull the data for your users to view, and then give then the ability to update, then all you need is an update statement in your recordset instead of pulling another recordset for your updating.

If you are using stored procedures to show the data to the user and then you want to do an update, then use the table. This would be my preference, since stored procedures are faster and they are read only. I ussually use them to navigate to the dataset that needs to be updated and only when there is an update do I call the table in a recordset.

Some times you have to use stored procbedures for inserts and updates as well. If you update an updateable view, all the constraints from the table will still apply. So if you only accept M or F for gender, this will still be the case if you update the view. Instead of triggers can be used with non updatable views, but triggers do have a performance drawback.

It really depends on your implementation.



Sal