The Business Intelligence Blog

November 9, 2010

SSIS TempStoragePath Error

Filed under: SSIS — Tags: , , — Shahfaisal @ 12:33 pm

This blog post has been moved to http://shahfaisalmuhammed.blogspot.com/2011/09/ssis-tempstoragepath-error.html


Advertisements

July 6, 2010

SSIS Error – The value violated the integrity constraints for the column

Filed under: SSIS — Tags: , , , — Shahfaisal @ 5:51 pm

This blog post has been moved to http://shahfaisalmuhammed.blogspot.com/2011/09/ssis-error-value-violated-integrity.html

 

January 21, 2010

Automate Integration Services Package using SQL Server Agent

Filed under: SSIS webcasts — Tags: , , , , , , , — Shahfaisal @ 12:40 am

How to: Automate SSIS Package Execution by Using the SQL Server Agent (SQL Server Video)

January 10, 2010

Late Arriving Dimension Rows

Many a times when loading fact data, you may find that for a fact record, the corresponding dimension record is not available. To get around this, a new row is inserted into the dimension table with the surrogate key and natural key as a placeholder record. These placeholder records are known as late-arriving dimension rows.

Example: At my current work place, we process our facts everyday and dimensions once a week . Now guess what will happen when a new employee joins and starts working from the next day? Since we do our time entry on a daily basis, this new employee’s hours will show up in the fact table(WIP table) but the corresponding dimension record(employee name etc) will be missing.

To summarize, late arriving dimension rows are:

  • added during fact processing when the business key from the fact source doesn’t have a match in the dimension table
  • updated during dimension processing when the dimension record comes in from the source

SQL Server’s Slowly changing Dimension Wizard refers to late-arriving dimension rows as Inferred Members. For more details on how to handle late-arriving dimension rows using SQL Server Integration Services(SSIS), please refer Slowly Changing Dimensions in Data Warehouse.

December 29, 2009

Creating Deployment Utility for Integration Services Packages

Filed under: SSIS — Tags: , , , , — Shahfaisal @ 1:26 pm

Before deploying Integration Services packages, you will need to create a Deployment Utility by configuring the project properties in Business Intelligence Development Studio(BIDS). The deployment utility creates a folder that contains all the files that you need to deploy the packages in a project. This utility is very helpful when you don’t want to deploy the packages manually. Please note that you have to create this utility if you want to use built-in deployment tools, however, if you intend to deploy the package manually or use SQL Server Management Studio(SSMS) to import the package, then you don’t need to create this utility.

To configure the project to create deployment utility, right-click the project name and select properties as shown in the figure below.

The project properties dialog box appears as shown in the figure below.

Lets go through the configuration properties:

AllowConfigurationChanges – This property specifies whether the configurations can be changed at installation time, default value is true.

CreateDeploymentUtility – This property specifies whether or not a deployment utility is created when the project is built. If set to true, the deployment utility will be created. Default value is false which means it will not be created.
I have no idea why the default value is false, if somebody knows why, please leave a comment.

DeploymentOutputPath – This property specifies the location where the Deployment Utility will be created. Note that this path is relative to the Integration Services project.

After setting the project properties, select Build from the main menu and click Build package to create the deployment utility as shown in the figure below.

To verify whether the deployment utility has been created, navigate to the \bin\Deployment folder and look for the .SSISDeploymentManifest file.

Once the deployment utility has been created, you will need to copy the contents of the folder (\bin\Deployment) to the server where you want to deploy your packages and double-click the .SSISDeploymentManifest file to launch the Package Installation Wizard. The Package Installation Wizard will walk you through the deployment process.

Older Posts »

Create a free website or blog at WordPress.com.