Tag: Reporting Services

It seems that every product that has an underlying database has documentation that says not to modify the schema?  Do you always pay attention to that warning? The PSS blog at Microsoft says that for Reporting Services you ought to definitely keep your hands off, and gives some good reasons why you should.

However what about those other products? Dynamics, SAP, JD Edwards, and other common types of software that many companies use. Can you modify them at all? Perhaps.

We hear about the build vs. buy debate in software, but there’s also the modify vs. workaround argument. I was reminded of that from the PSS blog. There are times that you might be tempted to change things in a database built a software company, or add objects to that database. In many cases this can be seen as action that voids any support contract with the vendor, and more often than not they won’t want to give permission to make changes.

I can understand that, as it can substantially increase the support costs for a software company. However I also think that a blanket policy prohibiting changes is a bad idea.

I think there are plenty of things that you can do, especially with the latest versions of SQL Server, that could be useful “touches” that improve the use of a database. Adding indexes judiciously to improve performance of some queries is one very light touch that can add tremendous benefits. Adding reporting objects in another schema could help you extend functionality to get more value from the software.

Touching a database that you didn’t build should be done carefully, lightly, and with a lot of testing, and it can be something that creates a much more valuable system.

Steve Jones

Is this a big deal? Michigan is the wrong shape, reported on Connect as a problem with the Report Builder 3.0. I guess is depends on whether or not you are showing Michigan in one of your reports. If you are, it’s probably a big deal, and no matter what data is on the report, plenty of people will never get beyond the incorrect shape.

Is this a critical bug? Is it a must fix for SP1? Does it deserve a high level of priority?

Triaging bugs like this and assigning a priority has to be extremely hard. On one hand this should be a simple fix, but after the maintenance plan fiasco in SQL Server 2005 SP2, I’ve heard a few SQL Server developers say there are no “simple fixes.” However this bug is not critical to most people; it won’t cause downtime or data loss. For those people that need it, however, it could be extremely critical. It also a little embarrassing for any report that has the wrong shape visible in a map control.

Should this be fixed before bugs that cause downtime? What if this takes 2 days and those bugs take 2 weeks? Or two months? You could easily get into the situation where a low priority bug keeps getting pushed back because there are more important issues to deal with. I’m not specifically talking about this bug, but rather using it as an example of an annoying, but otherwise non-critical issue.

As companies work on software, I’m sure there’s some developer on every team that finds items like this one to be very annoying bugs, and would probably just fix it if they had time. Or permission. To me, this is a great reason why you ought to give developers some free time to work on things that they find interesting. My guess is many little bugs like this that can be fixed quickly, would get worked into the schedule.

Developers like fixing things, and they like easy wins. Give them a chance to work on them.

Steve Jones