Every type of database design has a design methodology that corresponds to that type of design – highlighting and drawing upon the strengths of the design type. For example, when designing a relational database, the design tends to focus on entities and their primary and foreign keys. “The whole key and nothing but the key” is a popular saying among of relational database designers.
At its core, GroverDB is a hybrid database - a merger of the best of Object, Relational, and Graph database technologies - such that the design methodology includes aspects of each of these technologies.
- Object means that everything (every person, place, or thing) is stored as an Object and that Objects are organized into a hierarchy of Object Classes.
- Relational means that all the data can be worked with using normal SQL commands (Select, Insert, Update, Delete) if that's what you want to do (not required).
- Graph means that the relationships between Objects are flexible and visual - like a mind map.
The data may also be analyzed by Class, Status, History and Dimensions. GroverDB has only a few types of meta-data; but when well-designed, these basic building blocks create a powerful and elegant solution.
The database is the central repository of data. It’s hosted within the secure firewalls in the GroverDB servers. The database does the real work; all the other components simply connect to the database and display the data that’s requested.
Programmers can use the Microsoft SQL Server Management Studio (SSMS) to connect to the database for custom SQL work such as importing data, connecting GroverDB to other databases, or connecting your public facing website to your GroverDB database.
Importing data using SSMS is covered in the SQL Migration section of the Knowledge Base.