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

SQL Server 2008 R2 : Space Allocation Structures When a table or index needs more space in a database, SQL Server needs a way to determine where space is available in the database to be allocated. If the table or index is still fewer than eight pages in size, SQL Server must find a mixed extent with one or more pages available that can be allocated.

SQL Server 2008 R2 : Database Pages (part 2) - Row-Overflow Pages, LOB Data Pages If you want to store large amounts of text or binary data, you can use the text, ntext, and image data types, as well as the varchar(max), nvarchar(max), and varbinary(max) data types. Each column for a row of these data types can store up to 2GB (minus 2 bytes) of data.

SQL Server 2008 R2 : Database Pages (part 1) - Data Pages The page header contains control information for the page. Some fields assist when SQL Server checks for consistency among its storage structures, and some fields are used when navigating among the pages that constitute a table. Table 1 describes the more useful fields contained in the page header.

SQL server 2012 : T-SQL Enhancements - Windowing (OVER Clause) Enhancements The first windowing capabilities appeared in SQL Server 2005 with the introduction of the OVER clause and a set of four ranking functions: ROW_NUMBER, RANK, DENSE_RANK, and NTILE. In our discussion, the term “window” refers to the scope of visibility from one row in a result set relative to neighboring rows in the same result set.

SQL server 2012 : T-SQL Enhancements - The GROUPING SETS Operator (part 2) - Mixing and Matching, Handling NULL Values SQL Server returns NULL values to represent all values in high-level rollup rows. If you’re fortunate enough to be working with data that is guaranteed not to contain NULL values, life is good for you.

SQL server 2012 : T-SQL Enhancements - The GROUPING SETS Operator (part 1) - Rolling Up by Level, Rolling Up All Level Combinations The GROUP BY clause has been part of the SELECT statement syntax since the earliest dialects of T-SQL. You use GROUP BY to create queries that collapse multiple rows belonging to the same group into a single summary row and perform aggregate calculations (such as SUM and AVG) across the individual rows of each group.

SQL Server 2012 : T-SQL Enhancements - The INSERT OVER DML Syntax (part 2) - Consuming CHANGES You will now implement a modified version of the uspUpdateBooks in Example 5 that uses the new INSERT OVER DML syntax to capture and store historical data for updates that are appended to the Book table.

SQL Server 2012 : T-SQL Enhancements - The INSERT OVER DML Syntax (part 1) - A Filterable Alternative to OUTPUT…INTO INSERT OVER DML refers to a special syntax in which you wrap an INSERT INTO…SELECT statement around any data manipulation language (DML) statement (INSERT, UPDATE, DELETE, or MERGE) that has an OUTPUT clause, rather than using OUTPUT…INTO on the DML statement itself.

SQL Server 2012 : T-SQL Enhancements - The MERGE Statement (part 2) SQL Server is very smart about examining MERGE statements, analyzing different combinations of merge clauses, and automatically performing the appropriate type of join to return the source and target data needed on both sides of the operation.

SQL Server 2012 : T-SQL Enhancements - The MERGE Statement (part 1) The MERGE statement does just what its name says. It combines the normal insert, update, and delete operations involved in a typical merge scenario, along with the select operation that provides the source and target data for the merge.

Configuring SQL Server 2008 : Memory configuration (part 2) - Setting minimum and maximum memory values When SQL Server starts, it acquires enough memory to initialize, beyond which it acquires and releases memory as required. The minimum and maximum memory values control the upper limit to which SQL Server will acquire memory (maximum), and the point at which it will stop releasing memory back to the operating system (minimum).

Configuring SQL Server 2008 : Memory configuration (part 1) - 32-bit memory management Apart from installing 64-bit versions of Windows and SQL Server, there are two ways of providing SQL Server with more than 2GB of memory; using the /3GB option or using Address Windowing Extensions (AWE) with the /PAE option.

SQL server 2012 : T-SQL Enhancements - Date and Time Data Types (part 2) - Date and Time Functions All of the traditional date-related and time-related functions, including DATEADD, DATEDIFF DATEDIFF, DATEPART, and DATENAME, of course fully support the newer date and time data types, and several functions have been added as well.

SQL server 2012 : T-SQL Enhancements - Date and Time Data Types (part 1) - Date and Time Accuracy, Storage, and Format The date, time, datetime2, and datetimeoffset types are four date and time data types that were introduced in SQL Server 2008. These types should be used for all new database development in lieu of the traditional datetime and smalldatetime data types.

SQL server 2012 : T-SQL Enhancements - Table-Valued Parameters (part 2) Simply prepare an ordinary SqlCommand object , set its CommandType property to CommandType.StoredProcedure, and populate its Parameters collection with SqlParameter objects. These are the routine steps for setting up a call to any stored procedure.

SQL server 2012 : T-SQL Enhancements - Table-Valued Parameters (part 1) As the name implies, a table-valued parameter (TVP) lets you pass an entire set of rows as a single parameter to T-SQL stored procedures and user-defined functions (UDFs).

SQL Server 2008 R2 : Database Files and Filegroups (part 2) All databases have a primary filegroup that contains the primary data file. There can be only one primary filegroup. If you don’t create any other filegroups or change the default filegroup to a filegroup other than the primary filegroup, all files will be in the primary file group unless specifically placed in another filegroup.

SQL Server 2008 R2 : Database Files and Filegroups (part 1) Databases in SQL Server 2008 span at least two, and optionally several, database files. There must always be at least one file for data and one file for the transaction log.

Installing SQL Server 2012 : The Installation Process (part 4) - Post Installation Tasks After SQL Server 2012 is installed, additional settings need to be configured and tasks need to be completed to have a production-ready server. Some of these settings are geared toward fine-tuning the SQL Server instance for optimal performance.

Installing SQL Server 2012 : The Installation Process (part 3) - Installing SQL Server 2012 Through the Command Line, Installing SQL Server 2012 Through PowerShell You can also use PowerShell to perform unattended installs. Simple PowerShell scripts can be written to execute SQL Server 2012 Setup through its command-line interface.

Installing SQL Server 2012 : The Installation Process (part 2) - Installing SQL Server 2012 Through the Installation Center The Installation Center is perhaps the easiest and most common way to install and modify any SQL Server installation. To initiate the installation of a new SQL Server 2012 standalone instance trough the Installation Center, follow these steps

Installing SQL Server 2012 : The Installation Process (part 1) - SQL Server 2012 Installation Center The Maintenance section provides shortcuts to do an edition upgrade, and to repair and update an existing SQL Server installation. It also allows you to remove a node from an existing SQL Server failover cluster.

Installing SQL Server 2012 : Preparing the Server, Selecting the Edition Selecting the right SQL Server Edition is another important consideration in the deployment plan because some editions have feature limitations and hardware support restrictions, while other editions are geared toward more specialized workloads..

SQL Server 2012 : SQL Server Architecture - SQL SERVER’S EXECUTION MODEL AND THE SQLOS In short, the SQLOS is a thin user-mode layer that sits between SQL Server and Windows. It is used for low-level operations such as scheduling, I/O completion, memory management, and resource management. To explore exactly what this means and why it’s needed, you first need to understand SQL Server’s execution model.

SQL Server 2012 : SQL Server Architecture - THE LIFE CYCLE OF A QUERY (part 3) - A Simple Update Query Now that you understand the life cycle for a query that just reads some data, the next step is to determine what happens when you need to write data. To answer that, this section takes a look at a simple UPDATE query that modifies the data that was read in the previous example.

SQL Server 2012 : SQL Server Architecture - THE LIFE CYCLE OF A QUERY (part 2) - Plan Cache Creating execution plans can be time consuming and resource intensive, so it makes sense that if SQL Server has already found a good way to execute a piece of code that it should try to reuse it for subsequent requests.

SQL Server 2012 : SQL Server Architecture - THE LIFE CYCLE OF A QUERY (part 1) It looks at a basic SELECT query first in order to reduce the scope to that of a READ operation, and then introduces the additional processes involved for a query that performs an UPDATE operation. Finally, you’ll read about the terminology and processes that SQL Server uses to implement recovery while optimizing performance.

Protecting SQL Server Data : CELL-LEVEL ENCRYPTION - Views and Stored Procedures (part 2) - Creating the Stored Procedures The final step in implementing these stored procedures is to grant the appropriate permissions to them. Requirement 6 allows the INSERT or UPDATE methods to be executed, if an encrypted column exists; only when the database role that performs the INSERT or UPDATE method has permissions granted to the key that performs the encryption.

Protecting SQL Server Data : CELL-LEVEL ENCRYPTION - Views and Stored Procedures (part 1) - Creating the View The sensitive data that is contained within the Borrower_Identification table is now protected with cell-level encryption. Our next steps are to create the views and stored procedures via which our users can interact with the Borrower_Identification table.

Protecting SQL Server Data : Implementing Cell-Level Encryption An optional argument when creating a certificate is ENCRYPTION BY PASSWORD. This argument defines a password protection method of the certificate's private key.