The Business Intelligence Blog

December 29, 2009

Mastering SQL Server Profiler

Filed under: SQL Server Database — Tags: , — Shahfaisal @ 11:42 pm

Here is an excellent free e-book for those of you who want to get a handle on SQL server profiler. Click here


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.

December 28, 2009

Web Intelligence Rich Client in Business Objects XI 3.x

The Web Intelligence Rich Client is just a standalone version of the Web Intelligence Java Report Panel that lets you work with Web Intelligence documents without connecting to the Central Management Server (CMS). This doesn’t mean that you only use Web Intelligence Rich Client in offline mode, you can also connect to CMS and work with Web Intelligence documents. In addition to the features offered by Web Intelligence Java Report Panel, you can also create reports based on personal data providers such as text or excel files using Web Intelligence Rich Client.

How to install Web Intelligence Rich Client
You need to set the default Web Intelligence report view to Web Intelligence Rich Client. Here is how you do it:
In InfoView, go to Preferences, click Web Intelligence, in the select a default creation/editing tool section, select Desktop (Web Intelligence Rich Client required) as shown in the figure below and click ok.

Now when you try to create a new document in InfoView, the Web Intelligence rich client will be downloaded and launched to create the document. As shown in the figure, you can also click the Install Now button to install it immediately.

December 27, 2009

Creating a package template in Integration Services

Filed under: SSIS — Tags: , , , — Shahfaisal @ 4:54 am

Many of you might have wondered how to create a package template in SQL Server Integration Services. There are no default templates available in SSIS, so you will have to create your own package containing everything that you want in a template such as connections, variables, configuration, common execute SQL tasks etc and then save it under the location:
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\ProjectItems\DataTransformationProject\DataTransformationItems

I know the path is not intuitive at all but thats how it is. After saving the package to this location you can reuse it as a template everytime you create a new package. You just have to right-click the project and select Add and then select New Item. A Visual Studio installed templates dialog appears as shown below.

Select the template and a name for the package and then click OK. A new package will be created that is exactly the same as the one created for the template.

Please note that the resulting package will have the same ID as the package template, so this could be a potential reason for issues later. Therefore, it is recommended to generate a new package ID each time you create a new package using package template. Please refer to the figure below for details on how to generate a new ID for the package.

December 26, 2009

Applying SQL Server Data Mining to Enterprise Business Problems

Filed under: Data Mining webcasts — Tags: , , , — Shahfaisal @ 9:10 pm

MSDN Webcast: Applying SQL Server 2005 Data Mining to Enterprise Business Problems (Level 300)

Older Posts »

Create a free website or blog at