logseq/pages/hls__JSSOFTWARE-D-23-00202_reviewer_1686845363323_0.md

file:: JSSOFTWARE-D-23-00202_reviewer_1686845363323_0.pdf file-path:: ../assets/JSSOFTWARE-D-23-00202_reviewer_1686845363323_0.pdf

• At the same time, they provide use benefits of working with the SQL and the NoSQL databases simultaneously. ls-type:: annotation hl-page:: 4 hl-color:: green id:: 649ca4b9-aa79-4413-ac91-46eeb8c5f8dc
• hybrid databases’ query optimisation ls-type:: annotation hl-page:: 4 hl-color:: green id:: 649ca4c5-3c26-44f3-b714-09a0cc0d1ced
• r, a process model for the application of hybrid statements’ optimisation was designed ls-type:: annotation hl-page:: 4 hl-color:: green id:: 649e88a7-6cd2-48fd-bdf2-5fd9cf1acb75
• extended architecture for work with the hybrid SQL/NoSQL databas ls-type:: annotation hl-page:: 4 hl-color:: yellow id:: 649e88c7-a2a2-48d6-a0ae-b8b62f20c7d8
• it is not always easy nor optimal to choose one data management technology. ls-type:: annotation hl-page:: 5 hl-color:: green id:: 649e91fc-ccf6-4562-af97-1dd6ecd1c84e
• hybrid databases enable integration and concurrent use of different technologies. ls-type:: annotation hl-page:: 5 hl-color:: green id:: 649e9240-4b40-4e81-a1b3-a5cc084a1e5a
• best functionalities of different database types ls-type:: annotation hl-page:: 5 hl-color:: green id:: 649e924b-0bc5-4cfa-b6a7-79af99908af1
• he following research questions led to the hybrid SQL/NoSQL database extension presented in this paper: ls-type:: annotation hl-page:: 5 hl-color:: green id:: 649e940e-5bd6-4f13-91d6-a49aad143466
• improve ls-type:: annotation hl-page:: 5 hl-color:: yellow id:: 649e9433-c26d-4d1d-b362-e82c9d89841f
• adjust the architecture ls-type:: annotation hl-page:: 5 hl-color:: yellow id:: 649e946d-4898-4ccc-bc4c-ed67d2d18d79
• duration of the statement execution ls-type:: annotation hl-page:: 5 hl-color:: green id:: 649e948f-4798-4f88-8411-1d2d56a0d863 hl-stamp:: 1688114321891
• e hybrid SQL/NoSQL databases and presented dedicated components of the extended ER model. ls-type:: annotation hl-page:: 7 hl-color:: green id:: 649e9baa-7f3a-4251-a8d5-38575eb8c9f0
• Section confirmed the purposefulness of further hybrid database optimisation research ls-type:: annotation hl-page:: 8 hl-color:: yellow id:: 649e9bca-6a93-4690-b524-e12377ec92bb hl-stamp:: 1688116177072
• herefore, none of the NoSQL database subtypes have their unique language. ls-type:: annotation hl-page:: 9 hl-color:: green id:: 649e9ca7-bd76-4ef1-b1ca-581976b855b0
• its decomposition and analysis. ls-type:: annotation hl-page:: 9 hl-color:: green id:: 649e9ce6-a2d9-4283-b819-905f0a9cd976
• e input statement (SELECT, INSERT, UPDATE, DELETE), the ls-type:: annotation hl-page:: 9 hl-color:: green id:: 649e9d3c-a5aa-4bb0-a1eb-b63bf20775f1
• ested statements (i.e. UPDATE with subquery or DELETE with subquery) is not supported by the current version of the architecture. ls-type:: annotation hl-page:: 10 hl-color:: purple id:: 649e9d59-bb93-4fe3-9ff8-2190926461ad
• parallel optimisation of different parts of the input statement. ls-type:: annotation hl-page:: 10 hl-color:: yellow id:: 649e9dd2-452c-4ec7-96e8-a47f83d53b72
• “multiple” records ls-type:: annotation hl-page:: 12 hl-color:: green id:: 649ea279-fba6-419e-9d15-79f55de27ebf
• . ls-type:: annotation hl-page:: 12 hl-color:: red id:: 649ea2a5-80c2-4d4b-87ab-95db901d8f3f
• As in the case of stating the hint for non-adequate and non-optimal indexes during query execution, the stated PARALLEL hint gets neglected, and the statement is executed without an error occurring due to the forwarded hint ls-type:: annotation hl-page:: 13 hl-color:: yellow id:: 649ea2e1-c889-413f-bb86-770c9c71ca0a hl-stamp:: 1688117991473
• hybrid database extension ls-type:: annotation hl-page:: 13 hl-color:: yellow id:: 649ea3ad-9bab-47b2-b016-1a130602119f
• At this time, creating a fully comprehensive solution for optimising all types of databases that a single hybrid can encompass is extremely challenging to do. It is not an easy task to determine the number of domain-specific languages used by all NoSQL databases currently available on the market. Even if there were an estimate, without the language standardisation by the leading NoSQL manufacturers, there would not be a comprehensive solution for implementing the optimisation techniques for the whole hybrid database. ls-type:: annotation hl-page:: 13 hl-color:: yellow id:: 649ea688-37eb-4efe-a3d1-853c4798294f
• [:span] ls-type:: annotation hl-page:: 14 hl-color:: yellow id:: 649ea7ad-938f-4d56-acc6-777ce8a3b251 hl-type:: area hl-stamp:: 1688119210696
• integration and uniform use of all hybrid database components ls-type:: annotation hl-page:: 13 hl-color:: green id:: 64a29c98-a362-44ae-8cfa-47c71f2f4f0d
• lack of support for the statement optimisation ls-type:: annotation hl-page:: 13 hl-color:: green id:: 64a29cae-b6b0-41ba-92ca-de1c150f7f65
• The motivation was to provide the comfort of using a single query language and to free the user from thinking about which component has requested data. ls-type:: annotation hl-page:: 13 hl-color:: green id:: 64a2e58c-bab3-4f30-9360-3b6f1cf7278d
• the whole hybrid database, with all its components, represents a single logical database. ls-type:: annotation hl-page:: 15 hl-color:: green id:: 64a2e622-e577-47b2-ab14-1117283772be
• consists fo ls-type:: annotation hl-page:: 17 hl-color:: red id:: 64a3d756-ef2f-49b7-9400-2b678a5716db
• Table 3 displays the use case id, a statement type, a destination component of the hybrid, a statement description and a statement syntax before and after applying the supported optimisation rules ls-type:: annotation hl-page:: 18 hl-color:: green id:: 64a3d84b-cb6b-490d-9d15-402fc8ace928
• Optimisation Rules repository structure ls-type:: annotation hl-page:: 16 hl-color:: red id:: 64a3d97f-362b-49a7-98fd-ebef7b13aa44
• as well as to show the effects of its use ls-type:: annotation hl-page:: 16 hl-color:: red id:: 64a3d9ce-f38f-4200-a01e-d99143306478
• What follows is the display and the analysis of the average execution times of the use cases chosen for testing, focusing on the execution times before and after the optimisation rules use. ls-type:: annotation hl-page:: 20 hl-color:: green id:: 64a3dacc-eb7d-4f2d-a8da-c6a5a3fbab07
• slight syntax adjustment. ls-type:: annotation hl-page:: 21 hl-color:: green id:: 64a3db91-ad7a-4313-9df4-2ead0ad100b4
• ncrease in the number of statement characters ls-type:: annotation hl-page:: 21 hl-color:: yellow id:: 64a3dbce-7ccf-4bb2-8280-40b9f7444822
• generalisation ls-type:: annotation hl-page:: 24 hl-color:: yellow id:: 64a3dc16-2f5f-4072-969b-2a52eeed144b hl-stamp:: 1688460312034
• However, the obvious trend observed was that the hybrid database with the SOC component required less time for test statements execution when the number of records increased, in comparison to the hybrid without SOC ls-type:: annotation hl-page:: 24 hl-color:: green id:: 64a3dc8f-37b3-4528-bf4f-209a289e55b9
• The current version still does not support the unified execution of multiple different statements (i.e. UPDATE with subquery or DELETE with subquery) ls-type:: annotation hl-page:: 24 hl-color:: yellow id:: 64a3dcc9-e85b-4fcd-b64d-6ea17254cea0