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 1 of 11, items 1 to 30 of 308.

How to Fix Left Truncation, Conceptually

Figure 1 shows several customers throughout time, on the line of time of calendar. Two dates are accentuated; the more is the left date of truncation early and the more is the day of the countable decree later. Only the customers who are in activity after the left date of truncation are in the database.

SQL Server 2012 : Other PerfMon Log Analysis Tools - Using SQL Server to Analyze PerfMon Logs

Analyzing large quantities of performance logs with SQL Server can be a useful solution when data analysis through other methods could be cumbersome and labor intensive.

SQL Server 2012 : Performance Analysis of Logs - Getting Started with PAL

The Performance Analysis of Logs (PAL) tool is a free utility for analyzing PerfMon counter logs and creating reports highlighting important areas by severity. The report color-codes counters to display problem areas based on thresholds defined by subject matter experts in the support teams at Microsoft.

SQL Server 2012 : Getting More from Performance Monitor (part 2) - Disk or Storage-Related Problems, SQL Server Performance Problems

Sometimes server hardware resources do not cause bottlenecks, but application performance is still bad. In this situation, it’s possible that internal SQL Server resources can become exhausted or depleted

SQL Server 2012 : Getting More from Performance Monitor (part 1) - Investigating CPU Problems, Investigating Memory-Related Problems

The availability of CPU cycles to service SQL Server in a timely manner is critical to database server performance. Configuration-based CPU bottlenecks may include max degree of parallelism, the cost threshold of parallelism, and mis-configured CPU hyperthreading.

SQL Server 2012 : Performance Monitor Overview (part 5) - Remotely Running PerfMon

Like many server management tools, an instance of PerfMon can be connected to a remote server for remote monitoring. This avoids the need to connect via Remote Desktop and may reduce the overhead of monitoring on the target server.

SQL Server 2012 : Performance Monitor Overview (part 4) - Working with Data Collector Sets

User-defined Data Collector Sets in Windows Server 2008 replace the Performance Logs and Alerts from Windows 2000/2003 but the principle is the same

SQL Server 2012 : Performance Monitor Overview (part 3) - Getting Started with PerfMon - Monitoring Real-Time Server Activity, Starting Out with Data Collector Sets

PerfMon is a component of Reliability and Performance Monitor which can be launched from Start ⇒ All Programs ⇒ Administrative Tools. Alternatively, just type perfmon into the Run box and press Enter.

SQL Server 2012 : Performance Monitor Overview (part 2) - New PerfMon Counters for SQL Server 2012

As shown in Table 1, a number of new PerfMon counters are available in SQL Server 2012. Some of these provide logging for new features such as AlwaysOn and FileTable, and some are more detailed counters related to memory utilization.

SQL Server 2012 : Performance Monitor Overview (part 1) - Reliability and Performance Monitor

PerfMon in Windows Server 2008 brings a new look and a new name for the parent snap-in, Reliability and Performance Monitor, although real-time performance monitoring retains the PerfMon name.

SQL Server 2012 : Knowing Tempdb - Configuration Best Practices (part 2) - Tempdb Initial Sizing and Autogrowth , Configuring Multiple Tempdb Data Files

A default installation of any SQL Server edition will create a tempdb database with an 8MB data file and a 1MB transaction log file. For a lot of SQL Server installations these file sizes won’t be enough, but they are configured to autogrow by 10% as needed.

SQL Server 2012 : Knowing Tempdb - Configuration Best Practices (part 1) - Tempdb File Placement

It’s quite a well-known best practice to separate data, transaction logs, and tempdb, and if you knew that already, are you sure you know why? The origin of this recommendation lies with the separation of types of workload between different physical storage, i.e. separate physical disks.

Microsoft SQL Server 2012 : Backup and Recovery Planning - System Databases Recovery, Performing a Complete Recovery

The master database contains key database and security information, and the msdb database holds the schedules and jobs for SQL Server, as well as the backup history. A complete recovery plan must include the system databases.

Microsoft SQL Server 2012 : Recovery Operations (part 4) - Restoring with T-SQL Code

A database backup is a regularly scheduled occurrence, so if SQL Server's built-in Maintenance Plan Wizard isn't to your liking, it makes sense to write some repeatable code to perform backups and set up your own SQL Server Agent jobs.

Microsoft SQL Server 2012 : Recovery Operations (part 3) - Restoring Individual Pages

The ability to restore pages has been available since SQL Server 2005; however, up until now, you needed to use T-SQL code. In this release you can perform this type of restore through a native interface inside Management Studio.

Microsoft SQL Server 2012 : Recovery Operations (part 2) - Performing the Restore with Management Studio

The Restore Database form, as shown in Figure 1, does a great job of intelligently navigating the potential chaos of the backup sequences, and it always offers only legal restore options.

Microsoft SQL Server 2012 : Recovery Operations (part 1) - Detecting the Problem , Recovery Sequences

If a database file is missing, clicking the database in Management Studio pops up a message saying that the database is unavailable. To further investigate a problem, check the SQL Server Errorlog.

SQL Server 2012 : Backup and Recovery Planning - Working with the Transaction Log

Sometimes it seems that the transaction log has a life of its own. The space within the file seems to grow and shrink without rhyme or reason. If you've felt this way, you're not alone. This section should shed some light on why the transaction log behaves as it does.

SQL Server 2012 : Backing Up the Database (part 2) - Backing Up the Database with Code,Verifying the Backup with Code

The BACKUP command offers a few more options than Management Studio, and using the BACKUP command directly is useful for assembling SQL Server Agent jobs by hand, rather than with the Maintenance Plan Back Up Database Task.

SQL Server 2012 : Backing Up the Database (part 1) - Performing Backup with Management Studio

The first backup must be a full database backup to begin the backup chain. You can perform a database backup from Management Studio, selecting the database to be backed up.

SQL Server 2012 : Executing Your Queries (part 2) - SQLOS - CPU Nodes, Schedulers, Tasks, Workers, Threads

A CPU node is a logical collection of CPUs that share some common resource, such as a cache or memory. CPU nodes live below memory nodes in the SQLOS object hierarchy.

SQL Server 2012 : Executing Your Queries (part 1) - SQLOS - Memory Nodes

The SQLOS memory node is a logical container for memory associated with a node, which is a collection of CPUs with shared memory. This can be either a “real” memory node, if the server has a NUMA architecture, or an artificial grouping that you created as a “soft” NUMA configuration.

SQL Server 2012 : Query Plans (part 3) - Reading Query Plans

Because you are looking at the inner workings of the Query Optimizer, and because this is a feature of SQL Server that is constantly evolving, installing any service pack or patch can alter the behavior of the Query Optimizer, and therefore display different results.

SQL Server 2012 : Query Plans (part 2) - Query Plan Operators

Join operators enable SQL Server to find matching rows between two tables. Prior to SQL Server 2005, there was only a single join type, the nested loop join, but since then additional join types have been added, and SQL Server now provides the three join types described in Table 1.

SQL Server 2012 : Query Plans (part 1)

Now that you have seen how your T-SQL is optimized, the next step is to look at the query plan that the Query Optimizer generated for it. There are several ways to view query plans, but perhaps the easiest is to view the graphical plan using SQL Server Management Studio.

SQL Server 2012 : Backup and Recovery Planning - Recovery Models (part 3) - Bulk-Logged Recovery Model, Setting the Recovery Model

The model system database's recovery model is applied to any newly created database. The full recovery model is the default for the Standard and Enterprise Editions. The Personal and Desktop editions use the simple recovery model as their default, but you can change the default by setting the recovery model for the model system database.

SQL Server 2012 : Backup and Recovery Planning - Recovery Models (part 2) - Simple Recovery Model, The Full Recovery Model

The simple recovery model is suitable for databases that require that each transaction be atomic but not necessarily durable. The simple recovery model directs SQL Server to truncate, or empty, the transaction log on checkpoints.

SQL Server 2012 : Backup and Recovery Planning - Recovery Models (part 1)

The recovery model configures SQL Server database settings to accomplish the type of recovery required for the database, as shown in Table 1. The key differences among the recovery models involve how the transaction log behaves and which data is logged.

SQL Server 2012 : Using XML Data - XQuery and FLWOR Operations

XQuery is a language that provides the ability to query structured and semi-structured XML data. XQuery is based on the existing XPath query language but includes added support for improved iteration, sorting results, and XML construction.

SQL Server 2012 : Using XML Data - FOR XML (part 3) - Explicit, Path

The PATH directive was introduced in SQL Server 2005 as an alternative over the EXPLICIT directive. The PATH directive is just as powerful as the EXPLICIT directive, but it is as simple to use as the AUTO and RAW directives.