Is there a way to export all Relational Models for a schema in Oracle Data Modeler to a single PDF file? Where each model is a separate page?
I have an ERD for my schema consisting of about 90 tables. This full model can be hard to read. To account for this, I have created several additional Relational Models that cover subsets of data. For example, another model that consists of just fives tables pulled from the full model, showing their mappings. This is to better demonstrate the relationships of this subset of data in our application's workflow. They relate to several other tables, but these five on their own more easily demonstrate how these items work together from a user's perspective.
I can print each relational diagram out to separate PDFs using File -> Print Diagram -> To PDF File..., but this leaves me having to manually combine nearly a dozen different PDFs. Is it possible to export them all out to a single file at once? Data Modeler seems to only focus on the open diagram that is in focus, and ignores everything else when I'm working with print options.
If that's not possible, is there at least a way to print all the models to separate files with a single click? Opening each model and printing them separately is overly time-consuming.
Not today.
What you can do, in version 4.2 is have your design/model with your smaller diagrams implemented as SubViews.
When you run the 'All Tables' report and export to HTML, you get a TOC/index page with links to the data dictionary reports for each object, and you also get links to each SubView diagram in the HTML. So it's a single report, with different pages for each diagram. It's just HTML instead of PDF.
It's NOT PDF, but I would argue slightly that HTML is easier to work with.
We could always create an ER to give you exactly what you're asking for though. I'm assuming that maybe Adobe Writer could take multiple PDF files and edit them into a single document as a workaround?
Related
In one of the SSAS solutions that I have inherent there are two cubes using the same data source and data source view. The data source points to database A. Database A contains the tables for both cubes. The issue at hand is that both cubes represent the data from two different ERP systems. Due to no plan upfront the situations occurred that one database contains the tables for both systems. The server hosting the database is going to be decommissioned, a good moment to reorder the things for the better.
On the new server I want to create separate databases for the ERP systems which results in two different databases containing the data for the cubes.
I now want to split the SSAS project in visual studio so both cubes have their own solution. In order to keep the relational model in the data source view intact I hoped it would be possible to split or copy the view or project.
So, how can I copy or split a SSAS project or datas ource view?
If there are better alternatives to deal with this situation I am open for those as well.
Well that was easy. I just had to create a new branch in Team Foundation Server and remove all projects and attributes that I do not need.
I have a lookup table that is harvested from the XML file and not physically stored in the MySQL database. Because of that all the data are represented in one word when it is queried out using jasper adhoc for example
ridikill
peon
thegreat
All these lookup should be like so
ridi kill
pe on
the great
how to make the data to show correctly in separate words.
You are going to have some trouble doing this exclusively in the Ad-Hoc editor, it simply doesn't have this kind of functionality on it's own. You could create a calculated field with the following code in the formula builder:
CaseWhen("RigType" == 'deepwaterdrillship', 'deep water drill ship', "RigType" == 'standardjackup', 'Standard Jack Up',"RigType"=='standardfloater','Standard Floater')
Replace all instances of "RigType" with your original field name. Obviously this will get quite manual if you have a lot of different strings.
If you created a calculated table in the domain/topic that you are using, with similar logic to the code above, this would be more powerful since you can join to your other tables. However, as Petter commented, this is a data source problem and in my experience it is always better to fix the source if possible.
Is there opportunity to use dataset with multiple tables as datasource in ActiveReports ? What advantages has ActiveReport over SSRS?
Datasets can only reference a single sql query results, they cannot be joined, you would have to join the tables in the SQL query itself. The results would appear as a single dataset that you can bind your data regions to.
ActiveReports has multiple designers and layout engines for various reporting scenarios. It has a section based layout (similar to Microsoft Access) and RDL continuous data regions layout and a Page Layout engine that is used for creating pre-designed form styles reports such as a tax form or complex insurance form. Each one of them has its own optimized engine.
In addition, AR provides you with the designers as royalty free controls to include with your applications. There are quite a few other unique features that might depend on your needs, such as an excel transformation device where the report data is rendered into an Excel template.
However, I would recommend that you download both and try them to see which one would fit your usage scenarios better.
Hope this helps.
http://activereports.grapecity.com
I'm not sure if I stated my question clearly, but I have two seperate pages and a single view model. Originally I only had one page, but I decided to split these up because my pages were getting too large (more specifically I had too many pivot items on a single page where two pages would seperate the data better for the user). I was wondering if it was possible to only load specific data to a single view from the view model, because as it is right now my application is freezing because my view model attempts to load all the data even though only about half of it needs to be used on the current page the user is viewing. If so, I'm assuming I would somehow need to let the view model know which data to load. How would I accomplish this. OR, is it good practice to create two seperate view models, one for each page, so that only the necessary data for each page will load accordingly and keep my application from freezing? I am not sure what the standard is here, or what is the most efficient in terms of CPU usage and response times, etc.
Loading more data than you need can definitely be a problem especially if you're doing it over the Internet. Why do it like that? Why not simply separate the viewmodel in two parts? The definition of VM basically says: (quote from Model-View-ViewModel (MVVM) Explained)
The viewmodel is a key piece of the triad because it introduces Presentation Separation, or the concept of keeping the nuances of the view separate from the model. Instead of making the model aware of the user's view of a date, so that it converts the date to the display format, the model simply holds the data, the view simply holds the formatted date, and the controller acts as the liaison between the two.
If you separated the view, you might as well separate the VM too in order to keep things simple.
Still, if that doesn't do it for you and your data is not exposed as a service of some kind, why not just using the parts of VM? Call only the methods you need according to the page which you're seeing, set only the properties you need, don't do it all. And do it on a different thread if the data is really large to process so that your UI doesn't freeze (and of course, in the meantime show the user that you're getting the data using a progress bar).
That should be enough for the scenario you described.
can someone please tell me or point me in the right direction regarding how to save a LINQ table to an excel spreadsheet?
Thanks!
Mr Cricket
Generally, there are two methods to Excel:
UI layer
A lot of UI controls, say Grids, such as XtraGrid (DevExpress.com), can show Linq result (actually you have to call IQueryable.ToList() at first) and then export what you see into excel, pdf, csv and other formats.
The advantage is you may adjust the UI represenation of the Linq data before you export it.
The disadvantage is that it is interactive, so user activity is involved.
Data Layer
You may write lines of code to export the data into MS excel directly. It should be very easy if you know the API of MS API. But if you want to make the sheet beautiful, you may need a lot of code. Or you may create an MS Excel template manually and show the data by the help of the template.
The advantage is the speed and no user is involved.
The disadvantage is that it is hard to make the export beautiful or conveniently. Especially when you offer this function to end users.