Structured Query Language (SQL) - Cultural View of Technology
Structured Query Language (SQL) - Cultural View of Technology Structured Query Language (SQL) - Cultural View of Technology
Log shipping 62 Log shipping In Microsoft SQL Server, log shipping is the process of automating the backup of a database and transaction log files on a primary (production) server, and then restoring them onto a standby server [1] . Similar to replication, the primary purpose of log shipping is to increase database availability by maintaining a backup server that can replace production server quickly. Although the actual failover mechanism in log shipping is manual, this implementation is often chosen due to its low cost in human and server resources, and ease of implementation. As comparison, SQL server clusters enable automatic failover, but at the expense of much higher storage and license costs. Compared to database replication, log shipping does not provide as much reporting capabilities, but backs up also system tables along with data tables, and locks standby server from users' modifications. [2] A replicated server can be modified (e.g. views) and therefore is not suitable for failover purposes. External links • Log Shipping [3] , MS SQL Server implementation. References [1] How to Perform SQL Server Log Shipping (http://www.sql-server-performance.com/articles/clustering/log_shipping_70_p1.aspx), "What is Log Shipping". Retrieved on 2008-12-16. [2] Ibison, Paul. "Log Shipping vs Replication" (http://www.sqlservercentral.com/articles/Replication/logshippingvsreplication/1399/). SQLServerCentral.com. . Retrieved 2009-08-07. [3] http://msdn.microsoft.com/en-us/library/ms190016(SQL.90).aspx
MaxDB 63 MaxDB Stable release 7.6.06.10/7.7.07.16 / March, 2010 [1] Operating system Cross-platform Type RDBMS License SAP freeware license agreement for MaxDB (closed source) Website [2] MaxDB is an ANSI SQL-92 (entry level) compliant relational database management system (RDBMS) from SAP AG, which was delivered also by MySQL AB from 2003 to 2007. MaxDB is targeted for large SAP environments e.g. mySAP Business Suite and other applications that require enterprise-level database functionality. It is able to run terabyte-range data in continuous operation. History The database development started in 1977 as a research project at the Technical University of Berlin. In the early 1980s it became a database product that subsequently was owned by Nixdorf Computer, Siemens-Nixdorf, Software AG and today by SAP AG. Along this line it has been named VDN, Reflex, Supra 2, DDB/4, Entire SQL-DB-Server and Adabas D. In 1997 SAP took over the software from Software AG and renamed it to SAP DB. Since October 2000 SAP DB sources additionally were released as open source under the GNU General Public License. In 2003 SAP AG and MySQL AB joined a partnership and re-branded the database system to MaxDB. In October 2007 this reselling was terminated and sales and support of the database reverted back to SAP [3] . SAP AG is now managing MaxDB development, distribution, and support. Source code of MaxDB is no longer available under the GNU General Public License. SAP also stated that "Further commercial support concepts to cover mission critical use requirements outside of SAP scenarios are currently subject to discussion." [4] Version 7.5 of MaxDB is a direct advancement of the SAP DB 7.4 code base. Therefore, the MaxDB software version 7.5 can be used as a direct upgrade of previous SAP DB versions starting 7.2.04 and higher. MaxDB is subjected to SAP AG's complete quality assurance process before it is shipped with SAP solutions or provided as a download on the 'SAP Network' [5] . Features MaxDB is delivered with a set of administration and development tools. Most tools are GUI based and have CLI (Command Line Interface) based counterparts. It offers bindings for JDBC; ODBC; SQLDBC (native C/C++ interface); Precompiler; PHP; Perl; Python; WebDAV; OLE DB, ADO, DAO, RDO and .NET via ODBC; Delphi and Tcl via Third Party Programming Interfaces. MaxDB is Cross-platform, offering releases for HP-UX, IBM AIX, Linux, Solaris, Microsoft Windows 2000, Microsoft Windows Server 2003, and Microsoft Windows XP. SAP users should check the details of the platform availability on the SAP product pages for the product that will be used together with MaxDB.
- Page 15 and 16: SQL 11 [9] ANSI/ISO/IEC Internation
- Page 17 and 18: SQL:2003 13 [11] http://www.iso.org
- Page 19 and 20: Advantage Database Server 15 • Sm
- Page 21 and 22: Call Level Interface 17 Call Level
- Page 23 and 24: Check Constraint 19 Check Constrain
- Page 25 and 26: Commit (data management) 21 Commit
- Page 27 and 28: Correlated subquery 23 Correlated s
- Page 29 and 30: CUBRID 25 Linux Foundation Silver S
- Page 31 and 32: CUBRID 27 References [1] http://www
- Page 33 and 34: Cursor (databases) 29 Scrollable cu
- Page 35 and 36: Cursor (databases) 31 Disadvantages
- Page 37 and 38: Data Definition Language 33 Data De
- Page 39 and 40: Data Manipulation Language 35 Data
- Page 41 and 42: Database Console Commands (Transact
- Page 43 and 44: Database Console Commands (Transact
- Page 45 and 46: Database Console Commands (Transact
- Page 47 and 48: DbForge Studio for MySQL 43 • Dat
- Page 49 and 50: Declarative Referential Integrity 4
- Page 51 and 52: Devgems Data Modeler 47 External li
- Page 53 and 54: Embedded SQL 49 External links •
- Page 55 and 56: EnterpriseDB 51 EnterpriseDB also o
- Page 57 and 58: Epictetus Database Client 53 Extern
- Page 59 and 60: Foreign key 55 SET NULL The foreign
- Page 61 and 62: FSQL 57 Comparator for Possibility
- Page 63 and 64: Hint (SQL) 59 Hint (SQL) In various
- Page 65: HSQLDB 61 Transaction support HSQLD
- Page 69 and 70: Meta-SQL 65 Meta-SQL 'Meta-SQL' Use
- Page 71 and 72: MySQL Workbench 67 MySQL Migration
- Page 73 and 74: MySQL Workbench 69 [14] MySQL Workb
- Page 75 and 76: Navicat 71 Free version Navicat Lit
- Page 77 and 78: PL/pgSQL 73 PL/pgSQL PL/pgSQL (Proc
- Page 79 and 80: PL/SQL 75 User-defined exceptions a
- Page 81 and 82: PL/SQL 77 A selection of other data
- Page 83 and 84: PL/SQL 79 Array handling PL/SQL ref
- Page 85 and 86: PL/SQL 81 Similar languages PL/SQL
- Page 87 and 88: Query optimizer 83 Join ordering Th
- Page 89 and 90: Query plan 85 Query plan A query pl
- Page 91 and 92: Rollback (data management) 87 Rollb
- Page 93 and 94: SQL CLR 89 External links • MSDN:
- Page 95 and 96: SQL Problems Requiring Cursors 91 S
- Page 97 and 98: SQL injection 93 Incorrect type han
- Page 99 and 100: SQL injection 95 mysql_query($query
- Page 101 and 102: SQL/CLI 97 SQL/CLI The SQL/CLI, or
- Page 103 and 104: SQL/Schemata 99 SQL/Schemata The SQ
- Page 105 and 106: SQLPro SQL Client 101 SQLPro SQL Cl
- Page 107 and 108: Scriptella 103 Scriptella Stable re
- Page 109 and 110: SQL/JRT 105 SQL/JRT The SQL/JRT, or
- Page 111 and 112: SQuirreL SQL Client 107 History The
- Page 113 and 114: Table (database) 109 An equally val
- Page 115 and 116: Truviso 111 Truviso Industry Softwa
Log shipping 62<br />
Log shipping<br />
In Micros<strong>of</strong>t <strong>SQL</strong> Server, log shipping is the process <strong>of</strong> automating the backup <strong>of</strong> a database and transaction log<br />
files on a primary (production) server, and then restoring them onto a standby server [1] . Similar to replication, the<br />
primary purpose <strong>of</strong> log shipping is to increase database availability by maintaining a backup server that can replace<br />
production server quickly.<br />
Although the actual failover mechanism in log shipping is manual, this implementation is <strong>of</strong>ten chosen due to its low<br />
cost in human and server resources, and ease <strong>of</strong> implementation. As comparison, <strong>SQL</strong> server clusters enable<br />
automatic failover, but at the expense <strong>of</strong> much higher storage and license costs. Compared to database replication,<br />
log shipping does not provide as much reporting capabilities, but backs up also system tables along with data tables,<br />
and locks standby server from users' modifications. [2] A replicated server can be modified (e.g. views) and therefore<br />
is not suitable for failover purposes.<br />
External links<br />
• Log Shipping [3] , MS <strong>SQL</strong> Server implementation.<br />
References<br />
[1] How to Perform <strong>SQL</strong> Server Log Shipping (http://www.sql-server-performance.com/articles/clustering/log_shipping_70_p1.aspx),<br />
"What is Log Shipping". Retrieved on 2008-12-16.<br />
[2] Ibison, Paul. "Log Shipping vs Replication" (http://www.sqlservercentral.com/articles/Replication/logshippingvsreplication/1399/).<br />
<strong>SQL</strong>ServerCentral.com. . Retrieved 2009-08-07.<br />
[3] http://msdn.micros<strong>of</strong>t.com/en-us/library/ms190016(<strong>SQL</strong>.90).aspx
Change language