Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
influent
Constraint Violating Yak Guru
367 Posts |
 Posted - 2008-07-09 : 15:12:52
|
| I have an SSIS package that has an Analysis Services Processing Task. The task processes all dimensions in a cube. The Analysis Services connection the task uses has an Expression set using variables for the server name and the database name. I have found a bug (I'm sure I'm not the first to find it) where Visual Studio saves my DTSX package in such a way that it always uses the values set at the time of creation rather than the variable values passed to it or set as the defaults. In another package I was able to get it working by deleting and recreating the AS connection, but I've deleted and recreated the connection and the task a few times in the one that's flaking out and it doesn't help. Anybody know how to fix this? |
|
|
influent
Constraint Violating Yak Guru
367 Posts |
Posted - 2008-07-09 : 15:23:11
|
| I found the bug in Microsoft Connect. For some reason they say they won't fix it, but I can't have the database hard-coded. Help!https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=251934 |
 |
|
|
influent
Constraint Violating Yak Guru
367 Posts |
Posted - 2008-07-09 : 17:07:46
|
| I solved my problem by using an "Analysis Services Execute DDL Task" instead, and using an xmla file as the source. I just have to tell my build scripts to update the DatabaseID correctly. |
|
|
|
|
|
|
default variable values being cached