官术网_书友最值得收藏!

Big database

Our current application has a mammoth database containing a single schema with plenty of indexes. This structure poses a challenging job when it comes down to fine-tuning the performance:

  • Single schema: All the entities in the database are clubbed under a single schema named dbo. This again hampers business due to the confusion with the single schema regarding various tables that belong to different modules; for example, customer and supplier tables belong to the same schema, that is, dbo.
  • Numerous stored procedures: Currently, the database has a large number of stored procedures, which also contain a sizeable chunk of the business logic. Some of the calculations are being performed within the stored procedures. As a result, these stored procedures prove to be a baffling task to tend to when the time comes to optimize them or break them down into smaller units.

Whenever deployment is planned, the team will have to look closely at every database change. This, again, is a time-consuming exercise and many times would turn out to be even more complex than the build and deployment exercise itself.

主站蜘蛛池模板: 扎鲁特旗| 谢通门县| 开原市| 武城县| 仙桃市| 城口县| 永泰县| 桐庐县| 肥东县| 常州市| 土默特右旗| 福清市| 江西省| 鞍山市| 喀喇| 清苑县| 华阴市| 江永县| 武宁县| 萝北县| 吉隆县| 屏东市| 吉水县| 吴旗县| 阿鲁科尔沁旗| 杨浦区| 洛隆县| 西峡县| 米易县| 牟定县| 黔西| 林口县| 新乡县| 安陆市| 寿阳县| 老河口市| 洱源县| 青河县| 灵寿县| 江源县| 临澧县|