Lost SSRS 2005 Encryption Key

Well here is great work around for you !

Step 1 : goto above tab in SSRS configuration wizard
Step 2 : Press Delete and remove Key
Step 3 : Use below command in cmd to take a backup of the key
RSKEYMGMT -e -f c:/mybackups/myRSkeybackup -p StrongPassword
Step 4 : Restore the key that you just backed up and it will run with your new password.

Enjoy :) SQL !

Step by Step setting Transactional Replication in SQL Server 2008 R2

There are 3 steps involved for Configuring the Transactional Replication:

1.Configuring the Distribution Database.

A database which contains all the Replication commands. Whenever any DML or DDL schema changes are performed on the publisher, the corresponding commands generated by  SQL Server are stored in the Distribution database. This database can reside on the same server as the publisher, but it is always recommended to keep it on a separate server for better performance. Normally, I have observed that if you keep the distributoion database on the same machine as that of the publisher database and if there are many publishers then it always has an impact on the performance of the system. This is because for each publisher, one distrib.exe file gets created. 

2.Creating the publisher.

The Publisher can be referred to as a database on which the DML or DDL schema changes are going to be performed.

3.Creating the subscriber.

The Subscribers the database which is going to receive the DML as well as DDL schema changes which are performed on the publisher. The subscriber database normally resides on a different server in another location.

How it works

Transactional replication is implemented by the Snapshot Agent, Log Reader Agent, and Distribution Agent. The Snapshot Agent prepares snapshot files containing schema and data of published tables and database objects, stores the files in the snapshot folder, and records synchronization jobs in the distribution database on the Distributor.

The Log Reader Agent monitors the transaction log of each database configured for transactional replication and copies the transactions marked for replication from the transaction log into the distribution database. The Distribution Agent moves the initial snapshot jobs and the transactions held in the distribution database tables to Subscribers.

Configuring the Distribution Database

Upgrade SQL Server 2005 to SQL Server 2008

Its easier, Run the install for SQL Server 2008 on your server, choose the upgrade option. You'll also want to run the SQL Upgrade Advisor. This tool can help you determine if you're using any deprecated SQL features and will alert you to any gotcha's you might encounter. Once upgraded, to take advantage of many of SQL 2008's new features and enhancements, you'll want to change the compatibility level of your databases from 90 to 100.

Upgrade SQL Server 2005 to SQL Server 2008 (Three easy steps):
1) Update Microsoft .NET Framework to 3.5 SP1
2) Install Hotfix for Windows X64 (KB942288-V4) Windows Installer 4.5
3) Upgrade SQL Server 2005 to SQL Server 2008

SQL 2005 backups on SQL 2008:
You can restore the 2005 backup with 2008 without any problems. The compatibility from this point of view is nice.Backward is not possible only with backup files

Attach/Detach support:
An option which works without too much hassles is manually detaching and attaching the database/log files,Supported.

Support for Data Transformation Services (DTS) in SQL Server 2008 R2:
Supported to some extent, http://msdn.microsoft.com/en-us/library/bb500440.aspx

Dts Conversion to SSIS:
You can start the Package Migration Wizard from three locations.
1) From SQL Server Management Studio. Connect to an instance of the SQL Server Database Engine, right-click the Data Transformation Services node in Object Explorer under Management\Legacy, and select Migration Wizard.
2) From Business Intelligence Development Studio. Create or open an Integration Services Project, right-click on the SSIS Packages node in Solution Explorer, and select Migrate DTS 2000 Package.
3) From the command prompt. Start DTSMigrationWizard.exe from the C:\Program Files\Microsoft SQL Server\100\DTS\Binn folder.