Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Problem with SSIS job running in SQL Agent Expand / Collapse
Author
Message
Posted Wednesday, February 20, 2013 9:18 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Yesterday @ 8:20 AM
Points: 35, Visits: 312
I'm new in BI and technology in general so bear with me. I completed a lot of work in our development environment and made SSIS packages, SSAS cubes, and created tables in our datawarehouse.
I have a SQL Agent job that simply runs an SSIS package that unprocesses and processes a cube at 7:55 every morning. I recently moved everything from our development environment to test by scripting everything and having a third party vendor run those on the test databases.
Everything went well except for the SSIS cube process job. It failed this morning and fails when I try to manually run it with the following error:

"Source: Unprocess Cube Analysis Services Execute DDL Task Description: Errors in the metadata manager. Either the database with the ID of 'FeeAnalysisModel' does not exist in the server with the ID of 'xxxx'<c/> or the user does not have permissions to access the object."

I can manually run the job on dev without running into that error, but it fails for some reason on test. I think I know part of the problem, just don't know how or why it's happening.
When I originally created the SSAS project, I named it "FeeAnalysisModel" but later changed it to "FeeAnalysis" When viewing the project files on my local machine, I can see that there is an Analysis Services Project file titled, "FeeAnalysisModel" and a file titled "FeeAnalysis"

There isn't an SSAS database called FeeAnalysisModel on the dev server so I can't understand why it would run on dev but not test.

Sorry for the long story. Any help or ideas would be greatly appreciated!
Post #1422146
Posted Thursday, February 21, 2013 9:57 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Yesterday @ 8:20 AM
Points: 35, Visits: 312
Nevermind, I fixed the problem. I didn't realize that changing the database name doesn't actually change the Database ID.
So I had to drop the SSAS db and deploy the SSAS db after changing the DB ID.
Post #1422682
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse