Problem

When trying to open / run an SQL Server 2005 SSIS package from BIDS (Business Intelligence Development Studio) or Dtexec.exe tool, the following error can occur:

Error 1 Error loading PACKAGE_NAME.dtsx: Failed to decrypt protected XML node "PackagePassword" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.

Solution

In order to solve this error can you change the ProtectionLevel property of the package from EncryptSensitiveWithUserKey to DontSaveSensitive.

It seems that this behavior occurs when you try to run the SSIS package by using a different computer or a different user account than the computer and user account that were used to create the SSIS package.

For more information regarding this error you can access this link:

http://support.microsoft.com/kb/904800

It is possible to have the following error message when trying to install SQL Server 2008 on Windows 2008 R2:

You must use the Role Management Tool to install or configure Microsoft .NET Framework 3.5 SP1.

And after:

Cause

This happens because Windows 2008 R2 operating system ships with the .NET 3.5.1 framework.

Full story »

Problem

When trying to send emails from SQL Server using using the sp_send_dbmail stored procedure the following error can appear (on SQL Server 2005 or 2008):

EXECUTE msdb.dbo.sp_send_dbmail
   @profile_name = 'PROFILE_NAME', -- Change This
   @recipients = 'recipient@domain.com',  -- Change This
   @Subject = 'Test Message generated from SQL Server DatabaseMail',
   @Body = 'This is a test message from SQL Server DatabaseMail'

Msg 14607, Level 16, State 1, Procedure sp_send_dbmail, Line 141

profile name is not valid

The Database Mail feature is installed and configured (the Database Mail feature is enabled and the necessary account and profile is created). As sysadmin the emails are send successfully using sp_send_dbmail stored procedure.

The problem appear when trying to call the sp_send_dbmail stored procedure as a non-sysadmin login. Also the executing non-syadmin login has been added to DatabaseMailUserRole role in msdb database.

Cause

This happens because the database mail profile is not set with public access and the login is not allowed to use the specified profile.

Full story »

Below it?s a simple schema to easy understand the difference between the Clustered and Non-Clustered Indexes:

Indexes can be created:

-Automatically

When you create a PRIMARY KEY constraint, a Unique Clustered Index on the column or columns is automatically created IF a Clustered Index on the table does not already exist and you do not specify a unique Non-Clustered Index. The primary key column cannot allow NULL values. 

When you create a UNIQUE constraint (UNIQUE KEY), a Unique Non-Clustered index is created to enforce a UNIQUE constraint by default.

An index created as part of the constraint is automatically given the same name as the constraint name.

-Manually

Created by the user to improve the performance.

More information can by found in the following Microsoft tutorial:

Below it?s a simple schema to easy understand the difference between the primary key and unique key.

For detailed information check the online Microsoft documentation.

Primary Key is a combination of Unique and NOT NULL Constraints so it can?t have duplicate values or any NULL. So, if the Unique key is defined on not null column(s), then it is essentially the same as the Primary Key and can be treated as an alternate key meaning it can also serve the purpose of identifying a record uniquely in the table.