On my SSMS 2008 R2, whenever I browse a cube through SSAS, I can easily select all my results (Ctrl+A) and copy/paste it (Ctrl+C & Ctrl+V) into a Excel spreadsheet. As so (notice how all the content gets highlighted):
When I attempt the same thing with SSM 2017, none of this works. I researched the problem; however, it appears as though this functionality got removed. Or is it just me?
(I know that I can connect my Excel spreadsheet to my source and do all my manipulations there, but since I always work on SSMS, it's easier if I can keep using it without opening an Excel file. Especially, since I don't always need to do some comparisons with a spreadsheet).
This is one of of quirks of SSMS. The Browse Cube option does not allow you to copy the results.
BUT, there is a work-around. From your Browse Cube screen, click the 'Design Mode' to get the actual MDX query
Now, open a new MDX query editor Window
In this editor, paste you MDX query and execute it.
Now, you should be able to copy the results.
Related
How can I read a Oracle reports .rdf? Is installing the Oracle Report Builder the only option, if so can someone share a link for it.
I need to read a .rdf file to see its content. The file is a Oracle report which gets the data from DB and creates a report.
You can open a RDF file in any text editor. It'll be awful, but it is searchable so - if you're interested in its query, just search for SELECT and you'll get it.
Otherwise, if you really need to see the layout etc., Reports Builder installation is the only option, as far as I can tell.
I can't figure out what is going on with my report in Access 2010. When I run it, all the queries and recordsources are generated and the report shows up, perfectly full of data and formatted in print preview. If I try and print a hard copy or export to PDF, the subreports don't print. I have done compact and repair, closed and opened, and check everything I know, but it's not working. The only thing that I can think of is that the subreports are based on temp tables I generate and set within VBA after I pull all the parameters I need. But I don't see why this would cause it to preview but not print? Any help would be greatly appreciated!!
Here's the solution I found... when I moved the table creation code to the button that prompted the report rather than having it use the openargs in the open event of the subreport, it worked. Don't know why exactly it liked it one place better than the other, but I'm glad that it works now!
After many hours in research and experimentation the only solution was a third party print function: http://www.lebans.com/reporttopdf.htm. Leben’s function always produces a printable PDF with visible subreports.
No modification of the report’s properties was of any value, though this is suggested by various posts; it failed to work for me. Similarly, compact and repair failed to help, as did the creation of a wholly new MDB file and importing all the forms/tables/queries. I ran the MDB in Access 2003 and in Access 2010 on another machine and had the same failure.
This points of course to the issue being embedded within Access. Research shows this has been an issue plaguing Access for many years; in its inimitable lack of care for users getting work done Microsoft has failed to even comment on this, much less fix it.
I had a similar issue and thought that I should post my fix in case someone else runs into the same problem.
I had a report with two subreports on it. From a form, I would select from several combo boxes and then hit the button to run the report. When the report opened (in preview and in report-view) it looked fine, and the subreports worked fine. However, when I tried to print or save, the subreports would not show up.
My solution was in my queries and in the form. The report's source queries were pulling criteria from the combo boxes on the form. Once the report was run, the combo boxes would clear, thus clearing the criteria for the queries. After the report is run, the report looks at the queries again when you try to print/save.
If you have a similar setup, I would suggest checking your source queries again after the report is run to see if you are still getting results. You should see the same data in your queries and in your report. If not, there's where to start looking. Hope this helps anyone else struggling with the same issue.
This is a very strange and perplexing problem I have never run across. I am working on an SSRS report that feeds off a database. I use an SSIS extraction package to append data to a table in said database. Everything seemed to work fine until the first time I updated the table. I can see the new data in SSMS, but the report looks like it is only seeing the data I had in there prior to the update. I've restarted Visual Studio, checked the connection string, and checked my dataset queries and I have no clue why the report is doing what it's doing.
If you are editing the report in Visual Studio, yes, it can be overly aggressive about caching the results of queries.
Look in the Solution folder (in file explorer, not Visual Studio) and look for a file with the name of the report, but .data appended, such as Report1.rdl.data.
Delete that file, which you can do while VS is running. Then preview the report again.
I have developed a report, which contains one matrix and one chart. The chart shows a line graph using the data in the matrix. When I preview the results, everything works fine. The matrix contains data and the chart shows corresponding line.
It also works when I deploy the report to my local instance of the reporting services (running on my PC).
However, after I publish the report to our "real" reporting services box, only the matrix part works (it shows all the correct data), the chart is blank and shows either an empty rectangle with a little image in the corner (when run report from my PC) or a red x (when I run report while logged in locally on RS box). This seems like some sort of setting or a security issue, but I can't figure out what it is.
As I suspected the issue was permissions. I ended up granting "Read" rights to the users on the entire Reporting Services program directory and I can now see my charts displayed. I will try to dig into it further to narrow down the directory where the permissions are needed, but at least I know where to look.
I think this can relate to the folder that reporting services use to write temp files to.
Example location: ...\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\RSTempFiles
I think there is an issue where files(s) can get locked in use and be read only in here. When you run a report, reporting services tries to write in here and fails. Because it includes dll files, it cannot write and use the relevant one to show a graph.
I tried moving the temp files manually but gave up trying to get the files not in use. The easy way out is to restart reporting services and this cleans the folder out. This worked for me. Obviously this is not the best option as you don't want to interrupt the service. If this really wasn't an option it would be best to persist with cleaning the temp files folder.
Since the SQL query box of an SSIS Lookup transformation is almost unusable, I usually write my code in SSMS (formatted with Redgate's SQL Prompt tool) and copy it to the Lookup.
When you close this window and later come back in, sometimes the formatting is preserved, but sometimes the carriage returns are replaced by the "square" character, as if the editor doesn't know how to display a carriage return, making the SQL unreadable. Copying it back into SSMS renders it perfectly readable again, and copying it back to the Lookup usually restores the formatting.
Any idea why the SQL box sometimes can't display the carriage returns properly? Is there any way to fix it, or is it just an annoyance you have to live with in SSIS?
Have you tried clicking on the 'SqlCommand' edit button in the property grid (in the 'Custom Properties' section)? I find that the string value editor that pops up renders the CRLFs correctly even when the object's native (custom) form doesn't.
F4 is a useful shortcut to jump to the properties list for the selected object, if it's not already showing.
Just an annoyance you have to live with in SSIS. I've encountered the same problem over and over again in other screens and googling it resulted in nothing useful.