I tried deploying an SSAS project under SQL 2005 dev server, but, deployment fails

This project is with multi data sources, multi cube - when I deploy, I get the following error:

Error 1 Either the 'MELLONBANK\ADCDT2Q' user does not have permission to create a new object in 'SMAMSQL5DEV', or the object does not exist. 0 0

I tried from SQL Server Management studio, I can create tables, write to it fine.

I asked the DBA whether permission problem - she said if SSIS is trying to write to file, there might be some problems, but, database creation shouldn't be a problem. My question is does SSIS try to write some XML when I deploy - my guess is it does with all the properties written in XML. Just trying to confirm with you guys!|||

I assume that you were actually talking about SSAS, not SSIS in your previous post.

The fact that you get this error when deploying an SSAS project means that you are not in the Admin group for SSAS. SSAS is different to the SQL Server relational engine and the fact that you could create tables/databases there does not mean that you have permissions to do this in SSAS.

You will need an Administrator (maybe the person who installed SSAS) to open up SQL Server Management Studio and do 1 of 2 things.

either.

1) Right click on the server, go to properties, click on the security option and add your user account - this will set you up as an SSAS administrator, which will let you create new databases.

Or

2) Create an empty database for you, add a role with your user account and set this role to have admin priviledges just on this database.

|||

My Admin has created an empty database and an Role for Me with Admin Permission,

but I am Still not able to Deploy the Solution with BIDS.

Error was "Für die XYZ-Datenbank wurde ein Identit?tswechselmodus festgelegt, der für Serveradministratoren reserviert ist."

if i freely translate to englisch "For the database xyz a identityimpersonationmode was set that is reserved for system administrators"

Whats wrong there?

Best Regards

HANNES

|||This has to do with how your datasource is configured. If you are not an admin, you cannot deploy a database that has a datasource with the identityImpersonate property set to something like ImpersonateServiceAccount. This is to prevent you possibly getting access to a connection with higher priviledges than your user account. You will either need to set the impersonation mode to another value. If you need it to be set like it is then you could get the admin to change it for you after deployment, the make sure you only deploy changed values or use the Database Deployment Wizard to deploy without the datasources.