Is there a way to automatically generate stored procedures out of the t-sql in the datasets found in an ssrs project?
There's not an automatic way to do this. You might be able to cobble something together to do it though. SSRS reports are in an XML format. The Datasets are in a < DataSets > element.
Unfortunately, I don't know how helpful it would be since the parameters would need to be resolved.
Someone created a Powershell to retrieve the dataset definitions from a report if you want to try to automate something. I think it would still need manual work to convert them - especially if they use parameters or have calculated fields.
https://ask.sqlservercentral.com/questions/94491/retrieve-dataset-definitions-from-ssrs-report.html
Related
When combining multiple fact tables using shared dimensions you need to use a drill-across query or a multi-pass query to get the correct results.
I'm looking for a BI tool that does this correctly based on recognising which tables are fact tables and which are dimension tables. The tool should preferably generate a postgreSQL query.
For most of the tools that I've been looking into, you need to recognise these situations and write SQL manually to fix this.
Are there any tools that will generate the correct queries for you without the need for writing the multi-pass or drill across yourself?
I am trying to run RAWSQL_REAL("select sum(amount_us)from gbsa_dpo_itg.Fact_tblHistoryData_new where qtr_data='Q42014'") in calculated field and I am getting error message ERROR 2133: Aggregate function calls cannot contain subqueries.
I am using tableau 8.3.3 and HP Vertica database live connection to tableau
When I run the same query in custom sql it is working fine
pleas help in this
thanks in advance
Read the manual about these functions, look under reference, functions
You don't generally pass an entire SQL string to execute in isolation. Instead, they are useful for writing expressions or calling non standard functions that your server may provide, which are embedded within the SQL that Tableau generates. So first learn to use Tableau to get the effect you want, and then resort to Raw SQL functions in the rare case where you need to access some database server specific feature.
There is no reason that you would need Raw SQL to get the information above using Tableau. You could put amount_us on the row shelf and qtr_data on the filter shelf, and Tableau would generate a similar query.
If you are doing this to combine data from multiple queries, first learn about calculated fields and data blending.
I have several tables I'm importing from ODBC using the import script step. Currently, I have an import script for each and every table. This is becoming unwieldy as I now have nearly 200 different tables.
I know I can calculate the SQL statement to say something like "Select * from " & $TableName. However, I can't figure out how to set the target table without specifying it in the script. Please, tell me I'm being dense and there is a good way to do this!
Thanks in advance for your assistance,
Nicole Willson
Integrated Research
Unfortunately, the target table of an import has to be hard coded in FileMaker up through version 12 if you're using the Import Records script step. I can think of a workaround to this, but it's rather convoluted and if you're importing a large number of records, would probably significantly increase the time to import them.
The workaround would be to not use the Import Records script step, but to script the creation of records and the population of data into fields yourself.
First of all, the success of this would depend on how you're using ODBC. As far as I can think, it would only work if you're using ODBC to create shadow tables within FileMaker so that FileMaker can access the ODBC database via other script steps. I'm not an expert with the other ODBC facilities of FileMaker, so I don't know if this workaround would be helpful in other cases.
So, if you have a shadow table into the remote ODBC database, then you can use a script something like the following. The basic idea is to have two sets of layouts, one for the shadow tables that information is coming from and another for the FileMaker tables that the information needs to go to. Loop through this list, pulling information from the shadow table into variables (or something like the dictionary library I wrote which you can find at https://github.com/chivalry/filemaker-dictionary). Then go to the layout linked to the target table, create a record and populate the fields.
This isn't a novice technique, however. In addition to using variables and loops, you're also going to have to use FileMaker's design functions to determine the source and destination of each field and Set Field By Name to put the data in the right place. But as far as I can tell, it's the only way to dynamically target tables for importing data.
I'm trying to share a set of parameters with several reports.
Is it possible to do that?
I currently have to create a set of parameters for each individual report. This creates duplicates of the same data, and makes it harder to maintain.
I am using SSRS 2008 R2.
Any help or direction on this would be greatly appreciated.
Thanks (^_^)
no, it is not possible because the parameters are directly linked to reports, like data sets. There are, on SSRS 2008 R2, shared data sets, the same way you have shared data sources. Maybe with them, you could try to do something like that (don't known, just guessing)
I use iReport designed jrxmls for Jasper reports
I have done database specific functions and DML queries like date format, string concatenation, concatenate symbol(||) etc.
My Question is, "Is there any way or plug-in to make the jrxml files to be database portable?".
Thanks in advance,
Kalaiselvan.
You are using JDBC, so your reports are already kind of portable unless you use some vendor-specific SQL functions or features.
You could write your OWN datasource in JasperReports (do implement JRDataSource interface), and provide your own layer of database independence. It shouldn't be that hard.
Each report is filled from a data source like a database, but you knew that. Since the report is filled by fetching data from a specific database with queries to specific rows, if you want to make your .jrxml files database portable (or your .jasper files for that matter) you will need to make your data source and sql queries parameters which are fed into your report file from your program. It is pretty straight forward to make the data source and SQL query a parameter using iReport.