|
|
| SQL Server Integration Services : Connection Projects in Visual Studio |
| Microsoft is trying to make it easier to get data sources or data targets defined and ready to utilize with SSIS packages. From Visual Studio, you can now create an Integration Services Connection project. A wizard takes you through defining the data sources and connections for an SSIS package. |
|
|
|
|
|
|
|
| SQL Server Integration Services : The SSIS Designer |
| The SSIS Designer is extremely easy to use and gives a user the flexibility of editing and manipulating any of the package properties in any order needed, as opposed to the strict sequential order of the SSIS Wizard. After you have mastered all the package concepts, you will find that you will be spending most of your time using the SSIS Designer instead of the wizard. |
|
| SQL Server Integration Services : Running the SSIS Wizard |
| The SSIS Wizard is a streamlined interface solely used to generate SSIS packages for importing or exporting data. It is really quite powerful and provides an easy but sophisticated way to move data from or to any OLE DB, ODBC, or text source to another OLE DB, ODBC, or text source |
|
| SQL Server Integration Services : A Data Transformation Requirement |
| Let’s consider a true-life data export requirement that is best served by using SSIS. The requirement is for a small business intelligence data mart (on SQL Server 2008) to be spun off each week from the main OLTP database (also on SQL Server 2008) that addresses a product sales manager’s need to see the total year-to-date business that a customer has generated |
|
| SQL Server 2008 : SSIS Tools and Utilities |
| SSIS includes several tools that simplify package creation, execution, and management. These tools are available within the Visual Studio/BI Development Studio IDE or integrated into other component-based tools . |
|
| SQL Server 2008 : SSIS Architecture and Concepts |
| You can think of SSIS as a data import/export/transformation layer in the overall system architecture that you are deploying for at least most of your Microsoft-based applications and a few non-Microsoft applications |
|
|
|
|
|
|
|
| Managing Security Within the Database Engine : Database Security |
| The database principals include database users, database roles, and application roles. These principals control a user's rights within the database. Keep in mind that you must map Windows and SQL Server principals to database principals for the Windows and SQL Server principals to have access to the objects within the database. |
|
|
|
| SQL Server 2008 : Performance Tuning - Locks, Blocking, and Deadlocks |
| Concurrency control is a vital part of any relational database management system and in SQL Server this is implemented primarily through Locking. Locking involves reserving resources (usually data pages) for a particular purpose; this can affect the availability of those resources. When a single task reserves lots of resources or runs for an excessive time blocking can occur, which affects system performance |
|
| SQL Server 2008 : Performance Tuning - Tracing |
| Half of performance tuning is finding the problem. System Monitor is the performance monitoring tool provided by Windows and this can be useful when measuring hardware performance or bottlenecks and useful in identifying the process on a server that is causing a slowdown |
|
|
|
|
|
|
|
|
|
| Encryption Catalog Views |
| Catalog views are a valuable tool in SQL Server, through which the metadata information of a database or an instance can be queried.
|
|
| Built-In Cryptographic Functions |
| A function is a database object that contains a block of code that can be referenced in a command to return either a single value, in which case it is called a scalar function, or a set of data, in which case it is called a rowset function.
|
|
| SQL server 2008 : Managing Security - Permissions |
| Designing a permissions strategy is important when properly securing database objects. Considering the hierarchy of securables—a database, a schema, or an object—you have options of applying permissions by either granting permissions on the database, on each schema within the database, or on each individual table or view.
|
|
|
|
| SQL server 2008 : Managing Security - Users |
| Users are database-level principals that are created in order to access resources within a database. Database Users are typically mapped to a login, certificate, or asymmetric key.
|
|
| SQL server 2008 : Managing Security - Roles |
| Like Windows groups, SQL Server provides two roles, server- and database-level roles into which logins and users can be added. Server-level roles are fixed roles that have a serverwide permission scope. Each built-in role serves a specific purpose and have the required permissions associated with them.
|
|
| SQL Server 2008 : Managing Remote Servers |
| Remember that remote servers are supported in SQL Server 2008 for backward compatibility only. (Remote servers are being deprecated!) By definition, a remote server is a server you access as part of a client process without opening a separate, distinct, and additional direct client connection. SQL Server can manage the communication between servers using Remote Procedure Calls (RPCs).
|
|
| Linked Servers |
| All these configuration options can also be done very easily with SQL Server Management Studio. The following sections occasionally describe that capability but focus on the SQL commands method because you will usually use this method in real-life production systems.
|
|
| Adding, Dropping, and Configuring Linked Servers |
| All these configuration options can also be done very easily with SQL Server Management Studio. The following sections occasionally describe that capability but focus on the SQL commands method because you will usually use this method in real-life production systems.
|
|
