- It is easy to view table relationships, constraints, indexes, stored procedure in database but triggers are difficult to view and track.
- Triggers run on every update made to the table therefore it adds more load to the database and cause the system to run slow.
- Triggers execute invisible to client-application application so it is difficult to figure out what happens at the database layer.
- It is hard to follow their logic as it they can be fired before or after the database insert/update happens.
- Triggers run every time when the database fields are updated and it is overhead on system. It makes system run slower
- It is easy to forget about triggers and if there is no documentation it will be difficult to figure out for new developers for their existence.
Connected Architecture of ADO.NET The architecture of ADO.net, in which connection must be opened to access the data retrieved from database is called as connected architecture. Connected architecture was built on the classes connection, command, datareader and transaction. Connected architecture is when you constantly make trips to the database for any CRUD (Create, Read, Update and Delete) operation you wish to do. This creates more traffic to the database but is normally much faster as you should be doing smaller transactions. Disconnected Architecture in ADO.NET The architecture of ADO.net in which data retrieved from database can be accessed even when connection to database was closed is called as disconnected architecture. Disconnected architecture of ADO.net was built on classes connection, dataadapter, commandbuilder and dataset and dataview. Disconnected architecture is a method of retrieving a r...
Comments
Post a Comment