These factors further accelerate the value and TCO of databases over time.
Describe the features, tools, and utilities of Structured Query Language (SQL). How can tasks be automated with SQL?
SQL has specifically been designed with features, tools and utilities to enable programmers to support nth-tier data architectures in addition to legacy client-server computing scenarios. The development and continual improvement of the features, tools and utilities of SQL for automating tasks have also been augmented to include auditing of programming tasks as well (Dadashzadeh, 2003). The functionality, features, tools and utilities of SQL have also been specifically designed to measure and improve performance as well (Mercioiu, Vladucu, 2010). The specific tools included in nearly all SQL language platforms include support for data migration via the ODBC interface (Melton, 1996), support for enhanced multi-table and data modeling support, and enterprise-wide migration of databases across diverse computing platforms (Melton, 1996). In addition to these developments, SQLs' features, tools and utilities also support advanced features including advanced programming and integration technologies. Now supported in the latest release are support for Active Service Pages (ASP), XML integration, legacy ODBC support, and support for a wide variety of scripting programs and utilities as well. All of these technologies taken together are also designed to compliment the legacy J2EE and .NET programming foundations of enterprise databases from Oracle, IBM and Microsoft respectively. Microsoft bases its SQL and data structure architecture on the .NET platform which has proven to be ideal for large-scale enterprise systems and mobile deployments (Jadhao, Bamnote, 2012). All databases support greater transaction support in the form of advanced crosstab and multi-tiered table structures as well. All of these factors taken together are what differentiate the SQL features, tools and utilities for the many other alternatives in the market today.
How is security implemented in a relational database?
The foundational security elements of a relational database include row and record locking, definition of access privileges by file, data and attribute type, and support for role-based access to enterprise-wide applications (Suciu, 2012). Security is implemented in relational databases through the use of restriction levels by attribute, and in recent releases of Oracle 11g Release 2, through the definition of resources and requirements by role and process workflow (Suciu, 2012). There are security and audit processes that are used for credential and login management in addition to identity verification processes that can track access to resources by role, restricting access to only those records relevant to get a specific series of tasks done (Ahlswede, Aydinian, 2011)
Summarize your findings by giving an opinion on the value of database management systems.
In conclusion, the role of DBMS platforms are to serve as a foundation for enterprise applications to scale reliably, securely and without interruption cross the entire spectrum of strategies a company relies on to grow (Ulusoy, 1998). The many implications of security and role-based access need to be balanced with the inherent agility possible in highly distributed, relational database structures that can drastically improve the competitive nature of any business. This is accomplished through the use of relational data models that are used for creating enterprise-wide applications to align and support, then streamline the processes that support and enable business strategies. Ultimately the many factors of a DBMS, from its security features to its support for SQL, revolve around the need for aligning information systems and sources to the needs and goals of the enterprise (Velicanu, Litan, Virgolici, 2010).
Ahlswede, R., & Aydinian, H. (2011). On security of statistical databases. SIAM Journal on Discrete Mathematics, 25(4), 1778-14.
Dadashzadeh, M. (2003). A simpler approach to set comparison queries in SQL. Journal of Information Systems Education, 14(4), 345-348.