Microsoft Certification Examples, exercises, practises, tutorials, solutions about Database

Change page: < 1 2 3 4 5 6 7 8 9 10 11 > | Displaying page 8 of 11, items 211 to 240 of 326.

The fundamental differences between SQL Server and SQL Azure lie in the basic design principals of cloud computing, in which performance, ease of use, and scalability must be carefully balanced

SQL Server 2008 : Performance Data Collection (part 2)

Data collection is configured using the MDW as the target for collected data. Data collection is performed on every configured server using a usermode process called dcexec.exe.

SQL Server 2008 : Performance Data Collection (part 1)

Performance data collection is one of the most significant new features for SQL Server Administrators. Performance data collection builds on the strengths of the DMVs to provide long-term data storage and reporting based on this data.

SQL Server 2008 : Performance Tuning - Partitioning

Organizations collect more data and retain data for longer than ever before. The phenomenal growth of the storage manufacturing industry over the past 10 years is a testament to continually increasing data collection

SQL Server 2008 : Guide to the DYNAMIC Management Views (DMVs)

DMVs are almost certainly the single most useful tool for troubleshooting and performance tuning for SQL Server databases. DMVs and DYNAMIC Management Functions (DMFs) provide Administrators with a simple yet powerful insight into the workings of SQL Server and hardware resources (disk, memory, CPU).

SQL Server 2008 : Managing Security - Service Accounts and Permissions

A few changes have taken place in SQL Server 2008 starting with the Windows local groups that have been a component of SQL Server installs prior to SQL Server 2008. The groups are still created but rights are no longer granted in SQL Server for them.

SQL Server 2008 : Managing Security - Security and SQL Agent

SQL Server job steps often need to do more than just execute Transact-SQL. In order to perform tasks such as operating system commands (CmdExec), executing Integration Services packages, and PowerShell scripts, various credentials often associated with Windows logins are necessary

SQL Server 2008 : Implementing Transactions - Transaction Traps

When working with explicit transactions there are a few statements you can use to control the transaction. The BEGIN TRANSACTION statement is what tells SQL Server that you are starting a new explicit transaction.

SQL Server 2008 : Implementing Transactions - Deadlocking

Deadlocks are a terminal locking issue that involves two transactions. When the deadlock occurs one of the transactions is killed and rolled back.

SQL Azure Primer (part 4) - Creating Logins and Users

With SQL Azure, the process of creating logins and users is mostly identical to that in SQL Server, although certain limitations apply. To create a new login, you must be connected to the master database

SQL Azure Primer (part 3) - Connecting with SQL Server Management Studio

Follow these steps to connect to your SQL Azure database using SQL Server Management Studio

SQL Azure Primer (part 2) - Configuring the Firewall

SQL Azure implements a firewall on your behalf. That's a benefit that helps protect your database. Indeed, the default firewall rule is that no one can connect. Allowing no connections by default is a good security practice

SQL Azure Primer (part 1)

As you've seen, SQL Azure is a relational database engine based on SQL Server technology. It supports many of the features of SQL Server including tables, primary keys, stored procedures, views, and much mor

SQL Server 2008 : Implementing Transactions - Locking

Locking is the method by which SQL Server controls who has what access to what data within the table. Every command that is run in the database takes some sort of lock against SQL Server.

SQL Server 2008 : Isolation Level Explained

Isolation levels are how SQL Server decides what level of locking to take when working with data. There are five isolation levels available for your transactions in SQL Server 2008: READ UNCOMMITED, READ COMMITED, REPEATABLE READ, SNAPSHOT, and SERIALIZABLE

SQL Server 2008 : ACID

ACID (Atomicity, Consistency, Isolation, and Durability) is the basic foundation upon which transactions are built. In order to be considered a transaction, the statement must fulfill these foundations.

SQL Server 2008 : Transactions Explained

Transactions are logical groups of commands that are committed to the database or rolled back in the database at the same time. This allows you to insert, update, and delete several different tables and revert those changes if a single command within the transaction fails, or commit all the work if there are no errors.

SQL server 2008 : Handling Errors (part 3)

SQL Server 2005 and 2008 provide you with a powerful error handling feature in your T-SQL code: a TRY and CATCH control of flow statement. This error handling technique is similar to exception handling, which exists in programmability languages

SQL server 2008 : Handling Errors (part 2)

The @@ERROR function returns the error ID number generated by the most recent statement executed by a user. If the value returned is zero, then no error occurred. This function is available in all versions of SQL Server, and it’s the only way to handle errors in version 2000 and previous of SQL Server.

SQL server 2008 : Handling Errors (part 1)

SQL Server 2008 : Indexing for Performance - Putting It All Together (part 5) - Filtered Indexes

For demonstration purposes, assume that the director of sales runs a daily report to see the number of sales and the Totaldue of sales for his region, and every time that query runs slowly, your boss gets a phone call.

SQL Server 2008 : Indexing for Performance - Putting It All Together (part 4) - Indexing JOIN Criteria

Next, you want to retrieve all the orders that contain a certain product. Let's query the SalesOrderDetail table to identify the records. Execute the following code sample.

SQL Server 2008 : Indexing for Performance - Putting It All Together (part 3) - Covering Your Queries

Now that you have your clustered indexes created, think about what will happen if you want to retrieve all of the orders in a given time frame. Let's run the following query. Figure 5 shows the execution plan.

SQL Server 2008 : Indexing for Performance - Putting It All Together (part 2) - Clustered Index Seeks

The first two index creations in Listing 1 create clustered indexes on the SalesOrderHeader and Product tables. Then comes a query. Then the listing creates a clustered index on the SalesOrderDetail table.

SQL Server 2008 : Indexing for Performance - Putting It All Together (part 1)

For the demonstrations in this section, we use a series of sales tables within the Adventure-Works2008 database. We would like you to create copies of those tables, move data into those copies, and create some indexes on them.

SQL Server Integration Services : Logged and Nonlogged Operations

Bulk-copy operations can occur in two modes: logged and nonlogged (also known as slow and fast bcp, respectively). The ideal situation is to operate in nonlogged mode because this arrangement dramatically decreases the load time and consumption of other system resources, such as memory, processor use, and disk access

SQL Server Integration Services : Using bcp (part 5)

If you are not making use of fixed-width fields or length prefixes, you must use a field terminator to indicate the character(s) that separates fields; for the last field in the data row, you must also indicate which character(s) ends the line.

SQL Server Integration Services : Using bcp (part 4)

The storage type is a description of how the data is stored in the data file. Table 2 lists the definitions used during interactive bcp and what appears in the format file.

SQL Server Integration Services : Using bcp (part 3)

bcp can handle data in one of three forms: character (ASCII), native, or Unicode. You have the choice of which character format is used, depending on the source or destination of the data file

SQL Server Integration Services : Using bcp (part 2) - Fundamentals of Exporting and Importing Data

One of the great things about bcp is its ease of use. This section runs through a couple simple examples and provides full explanations. All tables used here can be found in the AdventureWorks2008 sample database supplied by Microsoft in SQL Server 2008.