SQL Server Relational Database

2009 ◽  
pp. 263-347
Keyword(s):  
Relational Database ◽  
Sql Server

scholarly journals A generator of SQL schema specifications

2007 ◽  
Vol 4 (2) ◽  
pp. 81-100 ◽  
Author(s):  
Slavica Aleksic ◽  
Ivan Lukovic ◽  
Pavle Mogin ◽  
Miro Govedarica
Keyword(s):  
Information System ◽  
Normal Form ◽  
Relational Database ◽  
Sql Server ◽  
Database Schema ◽  
Intelligent Support ◽  
Case Tool ◽  
Design Environments ◽  
Data Constraints

IIS*Case is an integrated CASE tool that supports the automation and intelligent support of complex and highly formalized design and programming tasks in the development of an information system. IIS*Case, as a tool from the class of domain oriented design environments, generates relational database schemas in 3rd normal form with all relevant data constraints. SQL Generator is an IIS*Case tool that generates the implementation specification of a database schema according to ANSI SQL:2003 standard. The generator may also produce a database schema specification for Microsoft SQL Server or Oracle DBMSs. The paper describes SQL Generator's traits, considers aspects of its application, and shows its use in the implementation of a complex database constraint using procedural mechanisms of a particular relational DBMS. SQL Generator is implemented in Java and Oracle JDeveloper environment.

scholarly journals Analysis of the possibilities of optimizing SQL queries

2021 ◽  
Vol 19 ◽  
pp. 151-158
Author(s):  
Piotr Rymarski ◽  
Grzegorz Kozieł
Keyword(s):  
Relational Database ◽  
Web Applications ◽  
Query Language ◽  
Database Systems ◽  
Sql Server ◽  
Management Systems ◽  
Relational Database Systems ◽  
The Impact ◽  
Relational Database Management ◽  
Test Scenarios

Most of today's web applications run on relational database systems. Communication with them is possible through statements written in Structured Query Language (SQL). This paper presents the most popular relational database management systems and describes common ways to optimize SQL queries. Using the research environment based on fragment of the imdb.com database, implementing OracleDb, MySQL, Microsoft SQL Server and PostgreSQL engines, a number of test scenarios were performed. The aim was to check the performance changes of SQL queries resulting from syntax modication while maintaining the result, the impact of database organization, indexing and advanced mechanisms aimed at increasing the eciency of operations performed, delivered in the systems used. The tests were carried out using a proprietary application written in Java using the Hibernate framework.

SQL Server Relational Database

2012 ◽  
pp. 259-336
Author(s):  
Richard Kiessig
Keyword(s):  
Relational Database ◽  
Sql Server

The Key Factors of Mathematical Formula Affecting the Size of a Clustered Index

2014 ◽  
Vol 962-965 ◽  
pp. 2877-2880 ◽  
Author(s):  
Li Yue
Keyword(s):  
Relational Database ◽  
Database Management ◽  
Simple Formula ◽  
Sql Server ◽  
Key Factors ◽  
Mathematical Formula ◽  
Relational Database Management

In relational database management SQL SERVER 2012, we can estimate the size of a clustered index. But the steps of estimate the size of a clustered index is too complex. This paper gives you a simple formula to estimate the size of a clustered index and find the key variable of mathematical formula.

scholarly journals Proposal of a Relational Database (SQL) for Zoological Research of Epigeic Synusion

MENDEL ◽  
2021 ◽  
Vol 27 (1) ◽  
pp. 23-28
Author(s):  
Vladimír Langraf ◽  
Kornélia Petrovičová ◽  
Stanislav David ◽  
Zuzana Krumpálová ◽  
Adrián Purkart ◽  
...  
Keyword(s):  
Molecular Biology ◽  
Relational Database ◽  
Database Design ◽  
Sql Server ◽  
Biological Information ◽  
Ecological Relationships ◽  
Database Program

In recent years, developments in the field of molecular biology and genetics have led to the increase in biological information stored in databases. The same increase in the volume of information occurred in the field of zoology, but the development of databases was not addressed in this area. We prepared a relational database and its diagram in the Microsoft SQL Server Management Studio (SSMS) database program. Our results represent experience with construction of a new database design for the zoology field with a focus on research of epigeic groups. The structure of the database will help with meta-analyzes with the objective to identify zoological and ecological relationships and responses to anthropic intervention.

scholarly journals NoSQL contra SQL en la Administración de datos masivos: Un estudio empírico

2020 ◽  
Author(s):  
Francisco Rubio ◽  
Paul Vega . ◽  
Rolando P. Reyes Ch
Keyword(s):  
Response Time ◽  
Data Base ◽  
Relational Database ◽  
Rapid Response ◽  
Sql Server ◽  
Software Project ◽  
Related Database

When developing a software project, it is important to choose the data base that best suits the needs of the project, whether it is relational or non-relational. This article compares the efficiency of these two types of databases in handling input and reading large amounts of data, using the SGDB MongoDB 3.2 and Microsoft SQL Server 2016. Concluding that, in projects where the handling of a large amount of data and a rapid response are primary requirements, it is better to use a non-relational database. In contrast, if the project requires the use of relationships between entities, without giving greater importance to the response time, it is better to opt for a related database. Resumen: Al momento de desarrollar un proyecto software es importante escoger la base de datos que mejor se ajuste a las necesidades del proyecto. Las opciones de un técnico pueden estar entre una base de datos relacional o no relacional. El presente artículo compara la eficiencia de estos dos tipos de base de datos desde el punto de vista de la entrada y lectura de grandes cantidades de datos. Utilizamos a SGDB MongoDB 3.2 y Microsoft SQL Server 2016 para este estudio empírico. Concluimos que, en proyectos donde el manejo de una gran cantidad de datos y una respuesta rápida son requerimientos primordiales, y considerando estas variables, consideramos que podría ser idóneo el uso de una base de datos no relacional. En contraste, si el proyecto requiere el uso de relaciones entre entidades, sin dar mayor importancia al tiempo de respuesta, podría ser mejor optar por una base de datos relacional.

Sign in / Sign up

Export Citation Format

Share Document