I don't really know of anything better so this is mostly just pointless ranting; but I'll justify it to myself by saying at least you'll know what you're getting into if you've read this before you start. SSRS seems to be more "death by one thousand paper cuts" than completely broken, so it's not so easy to say "it's shit, shalln't use it" like any good prima-donna developer would. Sorry I mean rock-star (recruiter speak). It also offers a few features that would be pretty hard to code from hand cost-effectively in something like asp.net mvc, such as user editing, multiple export formats, scheduled emails, and some of the ways you can cut-and-shut the data in the reports.
I make no apologies for the colourful language, it's a representation of the emotional side of having to use this heap of crap.
- doesn't bind to a port like a normal fukcing service
- http server api (aka http.sys)
- list reservations:
- `netsh http show urlacl`
- auth in reporting https://msdn.microsoft.com/en-us/library/ms152899.aspx
- reports in VS
- "Explicity add new role assingment for the account you are using and check every box in sight" ~ a.n. colleague. lol
- ignore the .rdl.data files with git.
- no folders.
- renamed a dataset, nothing fucking broke!!!!!!!!!!!!!!!!!!!!!!!!!!! even though there are reports that depend on it. On editing the report's dataset list you can see clearly "not found", but yet it still runs. what in the blazes is that all about?
- caching in the report editor http://stackoverflow.com/q/3424928/10245
- kill the .data cache files http://stackoverflow.com/questions/3424928/in-ssrs-is-there-a-way-to-disable-the-rdl-data-file-creation
- git clean -xfd
- it's the `bin\` folder, not the .data files. Still, fuckkkk.
- to get from a report to a db you go, report > report dataset > shared dataset > db, but db is defined in the shared dataset with another name, which can be pointed to a shared data source, which is also named. and *that* data source actually has a connection string
- committing to tfs failed half way through because vs had locked a bunch of files I didn't even have open
- found a param with <Value>=Microsoft.VisualBasic.Strings.Join(Parameters!Stages.Label, ", ")</Value> - wtf.
- function overload matching warning wouldn't go away till I closed the sln
- localisation is a bitch
- http://stackoverflow.com/questions/10953629/how-to-change-ssrs-2008-locale etc
- why you no use User!Language??
- Visual Studio 2013 crashed. hard. while cancelling new report param
- adds 00:00:00 to date fields from sql server. duuuuuuuuuuuuh (goes via .net datetime internally, but even so, not friendly)
- changed date format, looks fine in VS, but no change in report server. wuh? deploy all
- no auto-sizing of cols http://stackoverflow.com/questions/7851045/ssrs-tablix-column-cangrow-property-for-width
- no nulls in multi-value http://www.keepitsimpleandfast.com/2012/03/how-to-pass-null-value-to-multi-value.html
- need dirty hack to show "all" rather than full list
- some fucking horror I've yet to encounter (querystrings) http://stackoverflow.com/questions/512105/passing-multiple-values-for-a-single-parameter-in-reporting-services
- it has a fucking canvas size that will push over to 2 pages
- the font kerning on a print is massively different to on web / design view
- "Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index " from editing xml. thanks for the error info. fuckkkkkers
- the ssrs gui editor is a flaky piece of shit
- doesn't select the right fucking textbox in the props window
- had to restart visual fuckigjn studio
- the underlying xml is fucking horrific
- <rd:Selected>true</rd:Selected> ----- what in the fucking blazes is that doing in there?
- how do you deploy without connecting visual studio to production server? you fucking don't hahahahahaa
- powerhell https://gist.github.com/timabell/7e3019bd2de802f0b259
- ssbi install croaked - https://support.microsoft.com/en-us/kb/2800050?wa=wsignin1.0
- [09:44:53] john doe: Tim can I have a .bak file of ReportServer$MSSQL2012TempDB which the stupid software seems to be unable to operate without even though it has Temp in the database name implying it will rebuild itself (at least that's what it implies to me)
- [09:47:48] Tim Abell: (facepalm)
- [09:47:49] Tim Abell: sure
- [09:48:08] Tim Abell: I did wonder, and then I thought, no they couldn't possibly need that
- dropdown doesn't work in firefox
- no debugging http://stackoverflow.com/a/14068447/10245
- Warning : The text box ‘appliedFilters’ and the image ‘urLogo’ overlap. Overlapping report items are not supported in all renderers.
- the only options for DRY in reports suck balls http://www.3pillarglobal.com/insights/tips-tricks-ensure-consistency-sql-server-reporting-services-reports
- http://harmful.cat-v.org/software/xml/ xml is a terrible format anyway
- layout is in inches
- you can change the layout to cm
- it stores different metrics (cm/in) for each element, wtf, pick a unit
- reflowing nicely is impossible
- layout engine is as intelligent as a piece of paper and a pen. x,y is all you get.
- this is the kind of bullshit that counts for helpful content on the net https://social.msdn.microsoft.com/Forums/en-US/86205ca4-13d0-4ca6-84f1-79797616f0f4/exclude-null-values-from-sum-and-avg-calculation?forum=sqlreportingservices - =sum(forum_format * quality_of_community) = errorrrrrrrrr
- multiple rdl xml schema in the same fucking project, completely different xml structure
- 2005 generated with "new report wizard" in VS 20-fucking-13: <Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
- 2008 <Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
- 2009 from https://technet.microsoft.com/en-us/library/cc627465%28v=sql.105%29.aspx - <Report xmlns:rd=http://schemas.microsoft.com/SQLServer/reporting/reportdesigner xmlns="http://schemas.microsoft.com/sqlserver/reporting/2009/01/reportdefinition">
- 2010 <Report xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner" xmlns:cl="http://schemas.microsoft.com/sqlserver/reporting/2010/01/componentdefinition" xmlns="http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition">
- how many fucking versions??!
- http://stackoverflow.com/questions/29951653/ssrs-2008r2-visual-studio-2008-and-2008-and-2010-schemas - how to not end up with old schema?!
- how do you upgrade a report schema? install a massive chunk of fucking sql server http://stackoverflow.com/questions/13170608/upgrade-my-rdlc-schema-from-2008-01-to-2010-01
- [17:54:48] john doe: Btw have you noticed that in Print Layout view the header doesn't expand if any of the textboxes have auto-grown? [17:55:14] Tim Abell: that's because ssrs is a piece of shit from 1990 [17:55:28] Tim Abell: and it thinks A4 is the ultimate display format [17:55:47] Tim Abell: you just have to guess how much space you'll need
- the ordering of the xml in the proj file is unstable causing diff noise
- subreports, icky http://bhushan.extreme-advice.com/subreport-in-ssrs/
- some things can only be achieved with subreports, and they have to be deployed separately from the main report, meaning they can get out of sync. enjoy the fear of not knowing if you'll break something else when you upload your new version of the subreport you depend on
- no support for "time" data type http://stackoverflow.com/questions/3846378/displaying-time-in-reporting-services-2008
- The "View Report" button next to the parameters when running a report in VS is *always* greyed-out, even though it actually works.
- wow that's mental, hidden reports show in details view and not in tile view in the ssrs web ui
- the report editor has a copy option for report items, but no paste, so you can't duplicate reports
- actually you can, but only if you know the keyboard shortcuts. 0_o - ctrl-c ctrl-v
- duplicating a report on the filesystem, and then using "add existing item" to include it puts it at the end of the list... until you rename it and then it's moved into alphabetical order causing a spurious diff. should have put in the right place in the first place. grr.
- using the cursor keys to move textboxes around is so laggy that I overshoot every single time
- the editor popups in visual studio are modal, so you can't refer to anything else
- and there's no maximise button so you have to drag the fiddly border to make it bigger
- the report editor hasn't heard of ctrl-c or ctrl-v, have to use ctrl-Ins / shift-Ins instead
- border rendering / precedence is a fucking mess. set some borders, your report will look like a two-year-old coloured it in, and how it looks changes depending on the zoom level.
- you have to use VB to do alternate row colours - http://stackoverflow.com/questions/44376/add-alternating-row-color-to-sql-server-reporting-services-report
- if anything goes wrong with an expression all you get is "#Error". Helpful. E.g. http://stackoverflow.com/q/9144312/10245
- this one time, at band camp, I edited a report definition in VS and it refused to save the new definition to disk (ctrl-shift-s, ctrl-shift-s!!). wtf. Restarted VS and all the changes were gone.
- report editor silently adds new parameters to the report when you add new parameters to the sql. seriously. fuck off.
- RSI-inducing UI for editing the reports. click click click clickity click
- the sql editor has only a single undo. like ye olde notepad.
- in the editor, you can right-click copy, you can't right-click paste. wtf. ctrl-v does paste though. wtf again. I know, I already said it, but it's reaaaaaly shit
- the field list on a dataset is ordinal, allowing you to mismatch the select in the sql from the list of fields in the dataset and not notice
- how do you align a textbox on the page?
- one goddam cell in the underlying format:
Contributed (thanks, a nice surprise!):
71. Report width limited to 455in (even if I'm hiding columns using parameters against the Visibility column filter).
72. NO DYNAMIC COLUMN CREATION (ridiculous!)
73. Selection of multiple columns and setting attributes is ridiculously flaky. This is because I wanted to reduce the column width and font to comply with Point 71 !!
74. We have to restart Reporting Server services frequently or our charts won't show up. Eh?
75. Cut and paste columns? Nope!
More recent things:
76. Disappearing "Report Data" menu: http://stackoverflow.com/a/28883272/1024
77. SSDT for VS2015 upgrades reports to 2016 schema as soon as they're opened (WAT?!) and ignores the TargetServerVersion being set to <=2014 http://stackoverflow.com/questions/37816216/deploy-of-a-report-with-ssdt-2016-generates-error what if we haven't upgraded our production server, hmmm?
78. Okay so when you run a build, VS2015 then downgrades the rdl to the right schema to match the project's target server version before putting it in the build folder. What could possssssibly go wrong. 0_o Complexity++
79. Install SSRS in only 41 easy steps https://thecodeattic.wordpress.com/category/ssrs/
80. Build > "Skipping 'SomeReport.rdl'. Item is up to date." - No it isn't, I've deleted it from the friggin bin folder. So clearly it has some stupid cache of what's it thinks is on disk rather than, oh I don't know fucking checking the disk. Sheesh. If it's that optimized why is everything still so damn slow?!
81. Building a project with lots of reports is slow. Even if nothing changed.
82. Intermittently get "[rsInvalidReportDefinition] The definition of this report is not valid or supported by this version of Reporting Services. The report definition may have been created with a later version of Reporting Services, or contain content that is not well-formed or not valid based on Reporting Services schemas. Details: Data at the root level is invalid." - I am not alone. https://connect.microsoft.com/SQLServer/feedback/details/2988044/randomly-get-rsinvalidreportdefinition-when-previewing-report - A rebuild fixes it for me, for a while at least.
83. Sometimes when you edit an embedded dataset it completely fails to persist any of your changes to disk. And when you close the report they are lost. Handy. Thanks fuck for git.
83. Assumes you've never heard of source control and creates numbered backups of report files (notably on auto-upgrade). Also has messages like "delete will permanently delete this thing" - no it won't I have source control; I wonder if the SSRS know what that is.
84. I've never managed to crash VS2015 so many times in one day. Omg you didn't click there did you? I wasn't ready! *crash* ... *again*
85. Change the files on disk and the preview window often doesn't notice
86. Preview window silently fires a 'build' of the reports. Sometimes.
87. Generates broken Shared-datasets http://stackoverflow.com/a/38753141/10245
88. If you break the xml of a shared-dataset the entire project will fail to load. w-t-f.
89. Renaming datasets etc just breaks everything rather than updating references.
90. The .rptproj file has a <state> tag at the top which is base64 encode xml (WAT?! xml in xml. eerrrrr), which is information about source control (arse-about-face or what! source code that controls the *source-control* [that controls the source, that controls the source-control that controls the source...]; even the words are circular!!). In the base64 you'll find a <SourceControlInfo> tag.
<Project xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" ToolsVersion="2.0">
decoded "state" contents:
<SourceControlInfo xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2" xmlns:ddl100_100="http://schemas.microsoft.com/analysisservices/2008/engine/100/100" xmlns:ddl200="http://schemas.microsoft.com/analysisservices/2010/engine/200" xmlns:ddl200_200="http://schemas.microsoft.com/analysisservices/2010/engine/200/200" xmlns:ddl300="http://schemas.microsoft.com/analysisservices/2011/engine/300" xmlns:ddl300_300="http://schemas.microsoft.com/analysisservices/2011/engine/300/300" xmlns:ddl400="http://schemas.microsoft.com/analysisservices/2012/engine/400" xmlns:ddl400_400="http://schemas.microsoft.com/analysisservices/2012/engine/400/400" xmlns:ddl500="http://schemas.microsoft.com/analysisservices/2013/engine/500" xmlns:ddl500_500="http://schemas.microsoft.com/analysisservices/2013/engine/500/500" xmlns:dwd="http://schemas.microsoft.com/DataWarehouse/Designer/1.0">
Enough xml namespaces for you?
91. The state base64 changes all the time causing diff noise.
I know I can't count, but if ssrs is going to make so little effort I don't see why I should. And to be honest "100" seemed a lot more like comic exaggeration when I titled my tomboy note which only had 5 or 6 grumblings in it, I wasn't actually expecting to get within spitting distance of the original number!
Doesn't mean I won't use it again mind, just don't promise to like it.
If you liked this, you might also like the ssrs deployment tool I sometimes look after: https://github.com/timabell/ssrs-powershell-deploy (mostly not my work, just pulled together a bunch of contributions).