IT tutorials
Change page: < 1 2 3 4 5 6 7 8 9 10 11 >  |  Displaying page 2 of 11, items 31 to 60 of 308.
SQL Server 2012 : Using XML Data - FOR XML (part 2) - Raw
FOR XML RAW is similar to FOR XML AUTO but with several differences. First, FOR XML AUTO does not enable you to alter the name of the elements in the resulting XML. Also, as you saw in the previous section, FOR XML AUTO names the elements after the name of the table or alias.
SQL Server 2012 : Using XML Data - FOR XML (part 1) - Auto
The AUTO directive is the easiest of the directives to use in which to generate XML output from results specified in the SELECT statement. Although it is certainly the easiest of the directives to use, it doesn't provide a lot of control over the resulting structure of the XML output.
SQL Server 2012 : Using XML Data - XML Data Type Methods
The XML data type supports a number of methods providing various operations on the XML document. An operation on an XML document is applied to one or more elements or attributes at a specific location. To perform an operation, the location of the specific element needs to be specified.
SQL Server 2012 : The XML Data Type (part 3) - XML Columns and Variables, XML Parameters and Return Values
We have seen through the previous examples how to use the XML data type in both columns and variables. You created a table with an XML data type column, created an XSD schema, and from that created an XML Schema Collection and applied the schema collection to the table.
SQL Server 2012 : The XML Data Type (part 2) - Typed versus Untyped XML, XML Schemas
XML validation is accomplished through the schemas, or XML Schema Definition language. The XSD language is a specific language used to validate XML documents (and fragments).
SQL Server 2012 : The XML Data Type (part 1)
Prior to SQL Server 2008, it was the responsibility of the application layer to produce the XML, and there was no consistent or defined way to produce the XML. Typically, it would use the XML API functions available in the programming languages to produce the desired XML, and if you have done it, it wasn't easy.
SQL Server 2012 : Query Optimization (part 4) - Influencing Optimization
Query hints are an easy way to influence the actions of query optimization. However, you need to very carefully consider their use, as in most cases SQL Server is already choosing the right plan.
SQL Server 2012 : Query Optimization (part 3) - Plan Caching and Recompilation
Once the Query Optimizer has come up with a plan, which may have taken a considerable amount of work, SQL Server does its best to ensure that you can leverage all that costly work again.
SQL Server 2012 : Query Optimization (part 2) - Understanding Statistics
Statistics provide critical information needed by SQL Server when performing query optimization. SQL Server statistics contain details about the data, and what the data looks like in each table within the database.
SQL Server 2012 : Query Optimization (part 1) - Parallel Plans, Algebrizer Trees
Rather than know all the details, you need only understand the bigger picture. Even this bigger picture is often too much information, as it doesn’t offer any real visibility into what the Query Optimizer is doing.
SQL Server 2012 : Query Processing - Parsing, Algebrizing
Query processing is performed by the Relational Engine in SQL Server. It is the process of taking the T-SQL statements you write and converting them into something that can make requests to the Storage Engine and retrieve the results needed.
SQL Server 2012 : Fault Tolerance - Configuring an AlwaysOn Availability Group (part 3) - Creating an Availability Group
The wizard can also handle the initial data synchronization for you. The next page in the wizard, shown in Figure 8, allows you to specify a network share on SQL-WEST to obtain the backup from or to skip the initial data synchronization altogether.
SQL Server 2012 : Fault Tolerance - Configuring an AlwaysOn Availability Group (part 2) - Configuring the SQL Server Instance
When the SQL Server Configuration Manager launches, click the SQL Server Services node, then select the Properties context menu of the SQL Server service account. Click the AlwaysOn High Availability tab, and check the Enable AlwaysOn Availability Groups check box, as shown in Figure 4.
SQL Server 2012 : Fault Tolerance - Configuring an AlwaysOn Availability Group (part 1) - Creating a Windows Server Failover Cluster
The first step is creating a Windows Server failover cluster group with SQL-EAST, SQL-SOUTH, and SQL-WEST. This step doesn’t have anything to do with the SQL Server instance; rather we are creating the Windows Server failover group containing these three Windows servers.
SQL Server 2012 : Fault Tolerance - High Availability Features in SQL Server (part 3) - Configuring Database Mirroring
Similar to when you use log shipping, you must perform a full database backup on the primary, copy the backup to the mirrored server instance, and restore the database using the WITH NO RECOVERY option within the BACKUP DATABASE statement.
SQL Server 2012 : Fault Tolerance - High Availability Features in SQL Server (part 2) - Replication, Database Mirroring
When the scope of the data that we want to replicate is almost the size of the database, we use features like log shipping or database mirroring to ensure we have two or more copies of the data.
SQL Server 2012 : Fault Tolerance - High Availability Features in SQL Server (part 1) - Log Shipping - Configuration
To configure log shipping in SSMS, right-click the UsedCars database, and select Ship Transaction Logs from the Tasks context menu. This will launch the UsedCars Database Properties dialog with the Transaction Log Shipping panel open.
SQL Server 2012 : Fault Tolerance - Defining a Service Level Agreement
If you randomly ask DBAs at a few companies how they manage their databases, chances are you will get a variety of answers in return. Some have the DBAs solely focus on the actual database and its performance; they are hands off of the backend storage.
SQL Server 2012 : Configuration Options (part 13) - Recovery-Configuration Properties
Even though SQL Server works with 8KB data pages, the operating system I/O writes in 512-byte sectors. Therefore, a failure might occur in the middle of a data-page write, resulting in only some of the 512-byte sectors to be written to disk.
SQL Server 2012 : Configuration Options (part 12) - Database-State-Configuration Properties
The database-state-configuration properties, as shown in Table 12, are available in SQL Server. These configurations are mostly used when a DBA performs maintenance on the database.
SQL Server 2012 : Configuration Options (part 11) - Trigger Configuration Properties
A trigger is a small stored procedure executed on an insert, update, or delete operation on a table. Triggers are nested when a trigger performs an action that initiates another trigger, which can initiate another trigger, and so on.
SQL Server 2012 : Configuration Options (part 10) - SQL ANSI–Configuration Properties
The connection default properties (there are several) affect the environment of batches executed within a connection. Most of the connection properties change SQL Server behavior so that it complies with the ANSI standard.
SQL Server 2012 : Configuration Options (part 9) - Cursor-Configuration Properties
The cursor threshold property sets the number of rows in a cursor set before the cursor keysets are asynchronously generated. The query optimizer estimates the number of rows that will be returned from the result set.
SQL Server 2012 : Configuration Options (part 8) - Configuring Database Auto Options
Use of auto_shrink can cause severe performance issues as it can cause index fragmentation as well disk fragmentation at the operating system level. It's generally best practice that you do not have this enabled on your databases.
SQL Server 2012 : Configuration Options (part 7) - Advanced Server-Configuration Properties
SQL Server 2008 introduced a new feature called FILESTREAM that enables you to store structured data in the database and associated unstructured (that is, BLOB) data such as text documents, images, and videos directly in the NTFS file system.
SQL Server 2012 : Configuration Options (part 6) - Connection-Configuration Properties
The Server Properties Connections tab (refer to Figure 5) sets connection-level properties, including defaults, number of connections permitted, and timeout settings.
SQL Server 2012 : Configuration Options (part 5) - Security-Configuration Properties
The same security-configuration options established during the installation are again presented in the Security tab of the Server Properties page, so the configuration may be adjusted after installation.
SQL Server 2012 : Configuration Options (part 4) - Processor-Configuration Properties
In a multi-CPU server, the operating system can move processes to CPUs as the load requires. The SQL Server processor affinity, or the relationship between a task and a CPU, can be configured on a per-CPU basis.
SQL Server 2012 : Configuration Options (part 3) - Memory-Configuration Properties
SQL Server can either dynamically request memory from the operating system or consume a fixed amount of memory. You can configure these settings on the SQL Server Properties Memory tab, as shown in Figure 2, or from code by means of the sp_configure stored procedure.
SQL Server 2012 : Configuration Options (part 2) - Startup Parameters
You use the startup parameters with the SQL Server services. The startup parameters are passed as parameters to the SQL Server program when the SQL Server service is started.
Top 10
Technology FAQ
- Microsoft ebs security server configuration
- IIs7 on Windows server 2003
- How to Configure Failover Clusters With Win 2008 Server R2?
- Windows 2008 Network Load Balancing
- Windows Server 2008 - Group Policy Management - Remove Computer Management
- Remove shortcuts possibility in a web page or to put in favorite
- HTA Dynamic Drop Down List
- IIS host header and DNS
- VMware or MS Virtual Server?
- Adobe Acrobat 9 inserting tab pages
programming4us programming4us