SSIS DEPLOYMENT

SSIS Packages can be deployed in 2 ways
1. File System Deployment
2. SQL Server Deployment
File System Deployment
This will install SSIS package and their dependencies to the specified folder in the file system.
SQL Server Deployment
This installs the SSIS package in SQL Server. This option is typically used if you use SQL Server for sharing SSIS packages between Servers. Package dependencies will be installed in a folder in the file system.
File System Deployment
Double Click the file having .SSISDeploymentManifest extension automatically takes to package installation wizard.

Click Next

Here we can choose the type of deployment. There is check box available in this page which enables us to validate the package after installation
Going ahead with File system Deployment takes you to a page where we can specify the location on which package to be installed

By default the location is Program Files\Microsoft SQL Server\100\DTS\Packages\Package_Name
We can change the location using browse button provided.
Click NEXT will take you to a confirm installation page

Click NEXT shows Finish installation page which contains the summary
-------------------------
SQL Server Deployment

Select SQL Server Deployment in wizard, click next

Give preferred authentication (Windows or SQL Server)
Entering proper username and password enables the browse button for selecting the package location.

Select the location to which the package has to be saved and click OK.

Click NEXT

Select the folder for installing the package dependencies and then click NEXT
After confirm installation page click NEXT

Click Finish.
Thus your package is saved in SQL Server.
You can view the package by connecting to SQL Server Integration service, expand stored packageMSDBspecific folder on which the package have been installed

NB:I am not able to paste the images of every step which I create for SSIS deployment steps

can Truncate Rolled back??

This is my very first blog and I got the inspiration to start only because of misunderstanding that exists on truncate command.
The question is can we rollback Truncate?
In many webistes and forums I found the answer to be a big NO and I know many who reading this blog have the same mind set.
The exact answer to the question is YES..Amazed??
we can verify the same by simple scripts
Just create a simple table insert some values truncate that and run rollback.
USE RKN
CREATE TABLE TEST(NAME CHAR('10'))
SELECT * FROM TEST
This will give an empty result
INSERT INTO TEST VALUES('RKNAIR')
GO 1000
Will insert 1000 records
Now I am truncating the table
BEGIN TRAN
TRUNCATE TABLE TEST
We can cross check whether the table got truncated by selecting the whole table.
SELECT * FROM TEST
This will give empty result as expected.
Now execute the rollback command
ROLLBACK
We can check the roll back worked by again issusing the select.
SELECT * FROM TEST
AMAZED????? :-)
Yes we can rollback Truncate.
Many believe truncate that truncate is a no logged operation which is far from truth. Truncate is MINIMALLY LOGGED and can be rolled back.
Hope this will help.

Please post your comments .