Database object
defined object in a database that is used to store or reference data. For example, a table or a sequence
A database object is a structure for storing, managing and presenting application- or user-specific data in a database. Depending on the database management system (DBMS), many different types of database objects can exist. The following is a list of the most common types of database objects found in most relational databases (RDBMS):
Tablespace, storage space for tables in a database
Tables, a set of values organized into rows and columns
Indexes, a data structure providing faster queries (at the expense of slower writing and storage to maintain the index structure)
Views, a virtual table that is made as it is queried
Synonyms, alternate names for a table, view, sequence or other object in a database
Stored procedures and user-defined functions
Triggers, procedures which are run automatically based on specific events
Constraints, a constraint on the domain of an attribute
User accounts, schemas and permissions
Database objects are permanent, which means that they remain in their form as long as they are not explicitly changed or deleted. Application- or user-specific database objects in relational databases are usually created with data definition language (DDL) commands, which in SQL for example can be CREATE, ALTER and DROP.
Rows or tuples from the database can represent objects in the sense of object-oriented programming, but are not considered database objects.
“Database object” enters the record as defined object in a database that is used to store or reference data. For example, a table or a sequence. Crown Archives preserves that source wording while asking what Database, object and defined can confirm, complicate or overturn.
Why this record matters
“Database object” is worth following because a concise public description often conceals a longer documentary argument. Here, Database, object and defined provides the most credible route into that argument.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Dec 5, 2024. The linked authority identifier is Q110832792. None of the 0 selected statements returned an explicit reference.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Database object”, its source revision and the description used here.
- Expand the search: follow Database object primary sources, Database object archive and Database research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Database object”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Database object” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.