Re :Re: DDL of an existing cube (Adrian Dumitrascu)

Hi!

Is there a way to get the DDL of a cube created with the AS wizard.

Thinks and regards.

You can get the DDL of any AS object, including a cube, very easily by connecting to your server in SQL Server Management Studio, right-clicking on the object and selecting one of the items under the 'Script <object> as' menu item.

HTH,

Chris

|||

Also, if you do not have the cube already deployed to AS2005, but you only have the BI project on which you created a cube with the wizard, you can right click on the cube item (in Visual Studio) and use 'View Code' option to see the XML.

Adrian Dumitrascu.

|||

Hi

I think i've to install a full version of SQL Server 2k to get access to SQL Server Management Studio.

Actually i've installed AS only and i'm using an Oracle DB as DWH.

TVM Chris for reply

Regards

|||

Hi

How Can i browse AS cubes within Visual Studio ( 6 ? .Net ? 2005?)

PS i'm using SQL2K AS

TVM for reply Adrian

Regards

|||

If you have Analysis Services 2000, then our suggestions won't work. Analysis Services 2000 doesn't have DDL scripts as Analysis Services 2005.

SQL Management Studio only works with AS2005, but not AS2000 (Analysis Manager remains the admin client for AS2000).

The same for BI projects (that you can create and edit in Visual Studio): they are a feature of AS2005 only. So there isn't a feature out of the box to browse AS2000 from Visual Studio.

Adrian Dumitrascu.

RDL to RDLC Dataset Bind Question

We got some existing Reports that are set to RDL files but now they want to be able to create a web user interface so the user can interact through such method. As I am finding out, these reports need to be converted to RDLC so that they can all the proper information so they can be binded. My question is, the datasets are already set (I beleive it's the .rdlc.data files) on the RDL solution project. Now I want transfer those DataSets to my Website project and bind those datasets to my Report Viewer Control. Is that the right approach? Or do we have to re-create the Datasets and then bind? Can I use Web Services to bind to these reports? Thanks for the input and all help is appreciated.

there is no need to do this what you need to do is to just deploythose reports on the reporting server then create web page and addreport viewer control to it to enable the user view the reports youdeveloped you can see this example to know how to do this

http://www.c-sharpcorner.com/UploadFile/asif.blog/DynamicDataGrouping08042006115320AM/DynamicDataGrouping.aspx

http://www.gotreportviewer.com/

RDA Pull with existing table

Hi Forum,

I am currently implementing RDA Pulls and Pushes. Both worked fine for me, except when I try to pull a certain table twice. I read that in order to pull the table a second time I must drop it on the client.

My original approach was to use a select statement with a where criterium in the pull statement (e.g. SELECT * from tblPhonebook where Pulled = 0), then set Pulled to 1 and pull again later.

My understanding of RDA was that I use the where criterium to filter the data at the server side and simply append that data at the client side.

Can I simply append data in some way or do I really have to drop the table on the client side every time I pull?

Regards
Tobias

you have to drop the table before the pull each time. some people solve this by introducing an inbox/outbox concept in your SQLCE/Mobile db. You RDA pull to the inbox table. you copy those rows over to your OLTP table that your mobile app intends to work against (which has same schema as inbox, except for the rda tracking columns). you post back the changes you made to the OLTP table to the inbox table (which now becomes an outbox). you push back to server, then drop the inbox/outbox table and repeat the process. burden to manage synchronization between the oltp table and inbox/outbox is on you.

this situation is really what merge replication is for.

-Darren

|||Thanks Darren,

I guessed it would be that way...

Regards
Tobias|||

I've been using the RDA pull successfully for years now. It's always been a problem that during or right before an RDA Pull there's a vulnerable period where the local table has been dropped but the RDA pulled table to replace it is not completely transfered. So if the connection breaks the local table is pretty much hosed. I read the above with interest and have often thought this would be the way to go. Any good links to a more detailed explanation of this technique? Anyone else out there using this successfully.

Another idea is to use the Select @.@.DBTS on SQLServer to get the last update deal and then bring back updates and news only without RDA but this seems convoluted....

RDA Pull with existing table

Hi Forum,

I am currently implementing RDA Pulls and Pushes. Both worked fine for me, except when I try to pull a certain table twice. I read that in order to pull the table a second time I must drop it on the client.

My original approach was to use a select statement with a where criterium in the pull statement (e.g. SELECT * from tblPhonebook where Pulled = 0), then set Pulled to 1 and pull again later.

My understanding of RDA was that I use the where criterium to filter the data at the server side and simply append that data at the client side.

Can I simply append data in some way or do I really have to drop the table on the client side every time I pull?

Regards
Tobias

you have to drop the table before the pull each time. some people solve this by introducing an inbox/outbox concept in your SQLCE/Mobile db. You RDA pull to the inbox table. you copy those rows over to your OLTP table that your mobile app intends to work against (which has same schema as inbox, except for the rda tracking columns). you post back the changes you made to the OLTP table to the inbox table (which now becomes an outbox). you push back to server, then drop the inbox/outbox table and repeat the process. burden to manage synchronization between the oltp table and inbox/outbox is on you.

this situation is really what merge replication is for.

-Darren

|||Thanks Darren,

I guessed it would be that way...

Regards
Tobias|||

I've been using the RDA pull successfully for years now. It's always been a problem that during or right before an RDA Pull there's a vulnerable period where the local table has been dropped but the RDA pulled table to replace it is not completely transfered. So if the connection breaks the local table is pretty much hosed. I read the above with interest and have often thought this would be the way to go. Any good links to a more detailed explanation of this technique? Anyone else out there using this successfully.

Another idea is to use the Select @.@.DBTS on SQLServer to get the last update deal and then bring back updates and news only without RDA but this seems convoluted....

RB - New table info didn't show up on the Report Builder report

Hi All - I'd like to add some more info to an existing RB report by adding a new table. I am able to add a new table to DSV and build relationship. I am also able to add the table to report model as a new entity and source fields. The report model gets rebuilt and redeployed without problem, and the old report still runs fine. But when I open the report in report builder and want to add more info, the new table/entity/attributes are not showing up at all.

I've had this problem before also, sometimes when I create a report model with multiple tables I can only drag and drop values from one table onto the report builder grid. Once I drag values from the one table there is no way to go back and add values from the other table.

Why is that?

|||

A report that already contains data displays the entities related to the data already in the report. If your new entity is not related to the data in the report, you will not be able to select fields from that entity and add them to your report. If the entities should be related, make sure you have created a Role in the report model that defines that relationship.