Showing posts with label SSAS. Show all posts
Showing posts with label SSAS. Show all posts

06/07/2014

Creating Parent-Child Dimensions

To create a parent-child dimension, add an attribute with a key column containing the parent id, and set the “Usage” to ‘Parent’. Optionally you can set the “NameColumn” to the column containing the name that should be displayed.

image

Adjust the property “RootMemberIf” to indicate which member is the root parent.

image

If you don’t want the parent to be repeated as a child of it’s own, you should set the property “MembersWithData” to ‘NonLeafDataHidden’.

image

In the end this should result in something like the following:

image

12/01/2011

SSAS port for named instance

 

Here is what I have learnt today while configuring the firewall to allow remote access to a named instance of SSAS.

You have to allow access through the firewall over port 2382. Subsequently you have to allow access over the specific port used by your named instance of Analysis Services.

But how can you determine on which port SSAS is running?

For that you have to open a command prompt and type in the following:

netstat /ao >>c:\output.txt

In the SQL Server Configuration Manager you have to look up the Process ID of your named instance of SSAS (for example: PID=2236).

Then you have to look for the PID in the output file and find the corresponding TCP IP:port information.

Once you know the port used by your named instance of SSAS, you have to make an inbound rule in the firewall to allow remote access to your named instance of SSAS.

Information about the SSAS ports can be found here. Also see my previous post about the firewall settings.

More information about these ports can also be found in “SQL Server 2008 Books Online” – “Configuring the Windows Firewall to Allow SQL Server Access”.

Ports used by Analysis Services

image_thumb1

image_thumb3[4]

11/01/2011

Deploy a SSAS project

 

When you create an SSAS project using BIDS / VS there are a number of files that are created in the bin folder of the project:

  • [project name].asdatabase - contains the declarative definitions for all SSAS objects
  • [project name].deploymenttargets - contains the name of the target SSAS instance and database
  • [project name].configsettings - contains environment specific settings such as data source connections and object storage locations.  These settings override what's in [project name].asdatabase.
  • [project name].deploymentoptions - contains options such as whether deployment is transactional and whether objects should be processed.

In order to deploy a SQL Server Analysis Services project to a server, you can use the Deployment Wizard included in SSAS as a tool to install the project.

1

Navigate to the [project name].asdatabase file in the bin folder of your BIDS /VS project or to the folder where you copied the files to:

2

Specify the target deployment server and the name of the SSAS database on that server. 

3

The best approach is to retain the settings made on the Analysis Server (SSAS deployment and Role-based security).

4

The best approach is to retain the configuration properties made by administrators. If necessary, you can overwrite them with the settings in the project.

5

Specify the connection details for the source database:

6

You can specify whether to process the SSAS objects after deployment. 

  • Default processing: let SSAS decide what needs to be done.
  • Full processing: to process all objects. 
  • None: to not process at all. 

7

Use the ‘Confirm Deployment’ dialog to optionally specify whether to generate an XMLA script.

8

Progress of deployment:

9

Deployment result:

10

10/01/2011

SQL Server installation and Firewall Settings

 

After installation of a SQL Server instance we need to make some changes to the firewall settings to make the SQL Server Database Engine externally accessible.

The following inbound rules should be made in the Windows Firewall:

  • Port 1433, Protocol TCP (Database Engine default instance)
  • Port 1434, Protocol UDP (SQL Server Brower service for a Database Engine named instance)

InboundRules

Now we should be able to connect to the SQL Server Database Engine.

To make the Analysis Services externally accessible, you need to open the following ports:

  • Port 2382, Protocol TCP (SQL Server Browser service for an Analysis Services named instance)
  • Port 2383, Protocol TCP (Analysis Services default instance)

More information about these ports can be found in “SQL Server 2008 Books Online” – “Configuring the Windows Firewall to Allow SQL Server Access”.

Ports used by the Database Engine

image

image

Ports used by Analysis Services

image

image

31/12/2010

SSAS deployment and Role-based security

 

When developing a SQL Server Analysis Services project, one normally deploys the project to a dev or test server before deploying to an acceptance or production environment to test the solution. After testing is completed, and once the solution has been deployed to the acceptance/production server, an administrator may change the role-based security.

When deploying an update of the solution, you have to decide if you want to retain those changes or if you want to overwrite them.

SSAS includes a tool called the Deployment Wizard which will allow you to do exactly what you want. When using the Wizard, one has to determine how existing security roles, permissions and role members are treated during deployment.

Default the Wizard suggests to overwrite the changes made by the administrator.

image

However if you select “Retain roles and retain members.”, you don’t overwrite the changes made by the administrator.

image