SQL Server 2008, SQL Server 2005, SQL Server 2003, SQL Azure, Oracle Tutorials

Change page: < 1 2 3 4 5 6 7 8 9 10 11 > | Displaying page 5 of 11, items 121 to 150 of 308.

SQL Server 2012 : XML and the Relational Database - Additional FOR XML Features (part 2)

Technically, an XML document must be contained inside of a single root element. You’ve seen many applied uses of FOR XML that generate all types of XML, but without a root element, the generated XML can only represent a portion of an XML document.

SQL Server 2012 : XML and the Relational Database - Additional FOR XML Features (part 1)

As of SQL Server 2005, xml is an intrinsic data type of SQL Server. Thus, you can cast the XML output from a FOR XML query directly into an xml data type instance, as opposed to streaming XML results directly or immediately to the client.

SQL Server 2012 : XML and the Relational Database - FOR XML Commands

FOR XML RAW produces attribute-based XML. FOR XML RAW essentially creates a flat representation of the data in which each row returned becomes an element and the returned columns become the attributes of each element.

SQL Server 2012 : XML and the Relational Database - The xml Data Type (part 2) - XML Schema Definitions

One very important feature of XML is its ability to strongly type data in an XML document. The XSD language—itself composed in XML—defines the expected format for all XML documents validated against a particular XSD.

SQL Server 2012 : XML and the Relational Database - The xml Data Type (part 1)

Using the xml data type, you can store XML in its native format, query the data within the XML, efficiently and easily modify data within the XML without having to replace the entire contents, and index the data in the XML.

Oracle Coherence 3.5 : Implementing Domain Objects - Adding support for schema evolution (part 2) - Implementing serialization for Evolvable objects

The Evolvable interface simply defines which information class instances need to be able to provide in order for the class to support schema evolution. The rest of the work is performed by a serializer that knows how to use that information to support serialization across multiple versions of a class.

Oracle Coherence 3.5 : Implementing Domain Objects - Adding support for schema evolution (part 1) - Implementing Evolvable objects

It is immediately obvious that the implementation of this interface will be the same for all evolvable classes, so it makes sense to pull the dataVersion and futureData attributes into a base class and define the getImplVersion method as abstract.

My SQL : The Binary Log - Binary Log Management

The events mentioned thus far are information carriers in the sense that they represent some real change of data that occurred on the master. There are, however, other events that can affect replication but do not represent any change of data on the master.

My SQL : The Binary Log - Logging Transactions (part 2) - Distributed Transaction Processing Using XA

MySQL version 5.0 lets you coordinate transactions involving different resources by using the X/Open Distributed Transaction Processing model XA. Although currently not very widely used, XA offers attractive opportunities for coordinating all kinds of resources with transactions.

My SQL : The Binary Log - Logging Transactions (part 1) - Transaction Cache

The binary log can have statements in a different order from their actual execution, because it combines all the statements in each transaction to keep them together.

SQL Server 2008 R2 : Database Snapshots - When to Use Database Snapshots

There are a few basic ways you can use database snapshots effectively. Each use is for a particular purpose, and each has its own benefits. After you have factored in the limitations and restrictions mentioned earlier, you can consider these uses. Let’s look at each of them separately.

SQL Server 2008 R2 : Database Snapshots - Limitations and Restrictions of Database Snapshots, Copy-on-Write Technology

The copy-on-write technology that Microsoft first introduced with SQL Server 2005 is at the core of both database mirroring and database snapshot capabilities.

SQL Server 2008 R2 : Database Snapshots - What Are Database Snapshots?

A database snapshot is simply a point-in-time full database view. It’s not a copy—at least not a full copy when it is originally created. We talk about this more in a moment. Figure 1 shows conceptually how a database snapshot can be created from a source database on a single SQL Server instance.

SQL Server 2008 R2 : Long-Running Transactions

As you have already seen, transaction information is recorded in each database’s transaction log. However, long-running transactions can be a cause of consternation to a system administrator who is attempting to back up and prune the transaction log. Only the inactive portion of the log can be truncated during this operation.

Planning and Installing SQL Server 2012 (part 6) - Installing SQL Server Evaluation Edition - Upgrading SQL Server

Chances are that if your organization has existing SQL Server implementations, you may eventually need to upgrade them. Each version of SQL Server (and almost any other software product) is officially supported for a limited number of years.

Planning and Installing SQL Server 2012 (part 5) - Installing SQL Server Evaluation Edition - Server Configuration Page, Database Engine Configuration Page

When SQL Server is installed, a few accounts are created before anyone connects to SQL Server. The SA account is the system administrator account and has access to everything within SQL Server. This is the highest privileged account, and its credentials should be protected. This tab allows you to enter a password for the SA account; be sure to provide a complex one.

Planning and Installing SQL Server 2012 (part 4) - Installing SQL Server Evaluation Edition - Options Tab, Setup Role Page, Feature Selection Page, Instance Configuration Page

SQL Server and its components like Analysis Services are not just their own products. They are sometimes integrated within other products like SharePoint 2010. It is the Setup Role Page shown in Figure 10, from which setup is asking you if you want to install all the SQL Server components, install the analysis services components within a SharePoint farm, or install everything with default options.

Planning and Installing SQL Server 2012 (part 3) - Installing SQL Server Evaluation Edition - Maintenance Tab, Tools Tab, Resources Tab, Advanced Tab

The Edition Upgrade Wizard allows you to upgrade an installation from a lower edition to a higher one. If you don’t know what is meant by “lower edition,” just think of how much each edition costs.

Planning and Installing SQL Server 2012 (part 2) - Installing SQL Server Evaluation Edition - Planning Tab, Installation Tab

There are other times within Setup where this System Configuration Checker will run for you. For example, when you are installing a stand-alone instance of SQL Server, this utility will be run at the beginning of that task.

Planning and Installing SQL Server 2012 (part 1) - Understanding the Editions, Planning Your Installation

If you are planning on installing SQL Server on your desktop to just play with it, you probably don’t create a plan, review it with other folks in your organization, and schedule a time to implement the plan. Chances are you load setup.exe and click the Next button a bunch of times until the wizard starts installing SQL Server.

MySQL for Python : Simple Insertion - A command-line insertion utility (part 3) - Calling main()

As the program stands now, it does nothing. It is simply a bunch of functions. While they call each other, there is nothing that instigates the execution process if the file is fed to the Python interpreter.

MySQL for Python : Simple Insertion - A command-line insertion utility (part 2) - Coding the other functions

The first three functions should validate input as: digital, alpha character string, or as a valid number on the table menu presented to the user.

MySQL for Python : Simple Insertion - A command-line insertion utility (part 1) - The necessary modules

Before we jump into coding, let us first assess which modules we need to import. The modules we need are listed next to our required functionality as follows. The need for MySQLdb is understood.

Oracle Database 11g : Connecting to Oracle - Use Oracle Configuration Files, Use Administration Tools

Remote applications will look for Oracle Net configuration files to determine how to access the Oracle database server. Configuration files can be found in the ORACLE_HOME/network/admin directory location.

Oracle Database 11g : Connecting to Oracle - Learn Naming Methods

A naming method defines the type of repository used to configure Oracle network information. This repository is accessed to define where the Oracle database server is located.

SQL Server : Common Problems with Data Integrity - Enforcing Data Integrity Using Triggers (part 3) - Accidentally overriding changes made by other triggers

As a defensive technique, before you start coding a trigger, it's well worth running a quick check to find out if any other triggers exist on the target table. To be even safer, after adding a trigger it is a good practice to check for multiple triggers on the same table for the same operation

SQL Server : Common Problems with Data Integrity - Enforcing Data Integrity Using Triggers (part 2) - Mishandling updates that affect the primary key

We have fixed one problem in our trigger, but it has another serious bug; it does not handle the case when the primary key column is also modified. Listing 7 demonstrates the problem. This time, the code also updates the ItemLabel column, which forms part of our Primary Key, as well as the Barcode column.

SQL Server : Common Problems with Data Integrity - Enforcing Data Integrity Using Triggers (part 1) - Problems with multi-row modifications

In the following example, our goal is to record in a "change log" table any updates made to an item's Barcode. Listing 1 creates the change log table, ItemBarcodeChangeLog. Note that there is no FOREIGN KEY on purpose, because the change log has to be kept even after an item has been removed.

SQL Server 2008 R2 : Transaction Logging and the Recovery Process (part 3) - Managing the Transaction Log

Each database in SQL Server has at least one transaction log file. The transaction log file contains the transaction log records for all changes made in that database. By default, transaction log files have the file extension .ldf.

SQL Server 2008 R2 : Transaction Logging and the Recovery Process (part 2) - The Recovery Process

When SQL Server is started, it verifies that completed transactions recorded in the log are reflected in the data and that incomplete transactions whose changes are reflected in the data are rolled back out of the database. This is the recovery process.