Deployment worked when it shouldn't have done

I've just had a situation where, when trying to process a cube, it failed because one of my Script Commands referenced a non-existent dimension.

Now I have no problem with that - its easily fixed. My problem is that the cube is obviously faulty so why was I allowed to deploy it? The deployment should surely have failed shouldn't it?

Is this a deployment bug?

Here is the script command:

Scope(Leaves([Currency]), EXCEPT( [Currency Conversion].[Currency Conversion].MEMBERS, {[Currency Conversion].[Currency Conversion].&[<None>]} ))

-Jamie

P.S. Does anyone from the SSAS team in Redmond frequent this forum?

The server has a very flexible, forgiving, and complex system for attempting to resolve name ambiguities. So if you simply provide the text [Currencty Conversion] it may be a dimension name or a hierarchy name or a level name or even a member name. (Yes, if the server can uniquely resolve this to a member name it will although a dimension prefix is a good idea at a minimum.) As a result, until the server has read the data during processing it does not fully bind the names and thus does not know for sure that this is a dimension name that cannot be found.

Yes, people such as myself from the SSAS team in Redmond do frequent this forum.

|||

Good to know - on both counts. Thank you Matt.

-Jamie

sql

Deploying many reports to different network

Hello,
We have a situation where we have a main reporting server on our main
network and a separate isolated network with it's own reporting server. There
is no external connectivity to the second network.
We need to be able to periodically synchronise the two servers (copy all
new/updated reports from the main server to the isolated server). We have
over 150 reports to transfer in this way (and only likely to increase), any
ideas on the easiest way to do this would be much appreciated. Is it a
question of copying the RDLs to the server and then running a script to
deploy the reports? Or can you backup and restore the RS databases?
Cheers,
--
BenHi Ben,
I would probably recommend following the strategy of writing a custom script
to extract all of the reports by enumerating through all of the report
objects - Reports, Datasources and Security settings etc. to extract them
out. Then write another script to migrate them to the new database.
From what I have seen the reporting service databases are fairly specific to
a machine/webfarm and it would be probably more trouble that it is worth to
just to a detach/attach.
regards,
Adrian.
"Ben S" <BenS@.discussions.microsoft.com> wrote in message
news:A8A126FA-C1CE-4126-972B-D4EBB28F0722@.microsoft.com...
> Hello,
> We have a situation where we have a main reporting server on our main
> network and a separate isolated network with it's own reporting server.
> There
> is no external connectivity to the second network.
> We need to be able to periodically synchronise the two servers (copy all
> new/updated reports from the main server to the isolated server). We have
> over 150 reports to transfer in this way (and only likely to increase),
> any
> ideas on the easiest way to do this would be much appreciated. Is it a
> question of copying the RDLs to the server and then running a script to
> deploy the reports? Or can you backup and restore the RS databases?
> Cheers,
> --
> Ben|||Or just follow MS suggested method of migrating an RS database :)
http://support.microsoft.com/?kbid=842425
"Ben S" <BenS@.discussions.microsoft.com> wrote in message
news:A8A126FA-C1CE-4126-972B-D4EBB28F0722@.microsoft.com...
> Hello,
> We have a situation where we have a main reporting server on our main
> network and a separate isolated network with it's own reporting server.
> There
> is no external connectivity to the second network.
> We need to be able to periodically synchronise the two servers (copy all
> new/updated reports from the main server to the isolated server). We have
> over 150 reports to transfer in this way (and only likely to increase),
> any
> ideas on the easiest way to do this would be much appreciated. Is it a
> question of copying the RDLs to the server and then running a script to
> deploy the reports? Or can you backup and restore the RS databases?
> Cheers,
> --
> Ben|||Thank you Adrian for both options.
I will leave this option as for now and try the scripting option first - I
should then be able to write it to only pick those reports modified after a
particular date to save transferring the whole lot each time.
Thanks again
Ben
"Adrian Russell" wrote:
> Or just follow MS suggested method of migrating an RS database :)
> http://support.microsoft.com/?kbid=842425
> "Ben S" <BenS@.discussions.microsoft.com> wrote in message
> news:A8A126FA-C1CE-4126-972B-D4EBB28F0722@.microsoft.com...
> > Hello,
> >
> > We have a situation where we have a main reporting server on our main
> > network and a separate isolated network with it's own reporting server.
> > There
> > is no external connectivity to the second network.
> >
> > We need to be able to periodically synchronise the two servers (copy all
> > new/updated reports from the main server to the isolated server). We have
> > over 150 reports to transfer in this way (and only likely to increase),
> > any
> > ideas on the easiest way to do this would be much appreciated. Is it a
> > question of copying the RDLs to the server and then running a script to
> > deploy the reports? Or can you backup and restore the RS databases?
> >
> > Cheers,
> > --
> > Ben
>
>|||Try 'RSScripter' from http://www.sqldbatips.com/ - it can create the
scripts and supporting files for you|||Thanks Parker, that looks very useful!
"Parker" wrote:
> Try 'RSScripter' from http://www.sqldbatips.com/ - it can create the
> scripts and supporting files for you
>