ReportServer scripting is probably the most complex but also the most powerful tool offered by ReportServer. In our newest tutorial we provide an introduction into scripting and the most common use cases.
To the tutorial: Getting Started with Scripting
Happy Scripting
In early April, MariaDB‘s CEO Michael Howard announced the development of the MariaDB ColumnStore with the words: “We’re uniting transactional and big data analytics all together under one roof. It’s the same MariaDB interface, security, SQL richness simplifying management. You don’t need to buy specialized hardware. It’s one unified platform.” (Read the full story on CIO.)
MariaDB’s ColumnStore is not entirely new. In 2014, InfiniDB (formally Calpont Corporation) ceased operations but not before releasing their column store technology (called InfiniDB and which was based on MySQL) under an open source license. MariaDB’s ColumnStore is based on InfiniDB and as the release notes say “most of the MariaDB ColumnStore code is unchanged”. We should thus expect no real leaps in comparison to InfiniDB but on the other hand can look forward to hopefully quite a mature and stable first release. A few days ago, the MariaDB team released a first alpha for testing and this is exactly what we did.
Testing a database is quite a challenge, as there are bazillion different use cases that you might want to include in your benchmark. For example, a huge plus of MariaDB’s ColumnStore is that it is fully SQL compliant and, in particular, ACID compliant. One way to test the system would thus be in an OLTP setup with numerous concurrently running small transactions. A second route would be to look at the analytical quality and consider not small transactions, but possibly long running OLAP type queries. In very large setups you might look at the performance of database clusters whereas the majority of projects will probably use only a single database node. Once you have decided on a certain test setup there is, of course, the question of how to measure the performance of the setup as this highly depends on the environment (what machine, how much RAM, disk speed, etc.). For this tentative test we decided to go the easy way: we have set up a single database node on a small virtual machine and used our analytics platform ReportServer to run a few OLAP type queries. We then did a comparative analysis and compared the performance of MariaDB’s ColumnStore against two other databases: the traditional MariaDB/MySQL InnoDB storing engine (to get a baseline) as well as the open source column store MonetDB.
The MonetDB column store has been around for quite a while (since 1993 according to their website) and is primarily developed at the Centrum Wiskunde & Informatica (CWI) in Amsterdam. While MonetDB is coming from academia (and admittedly has some quirks that you need to deal with) it has matured a lot in the previous years. In ReportServer it is supported as of version 3.0.
So in summary the setup is, MariaDB’s new ColumnStore vs. MonetDB (with MySQL InnoDB providing a baseline) on analytical queries within a restricted environment.
ReportServer’s flexible permission system perfectly lends itself to setting up multi tenant systems. In our newest tutorial we discuss how to setup such a system and how to reduce maintenance cost by utilizing user variables and scripting.
We are happy to announce the release of ReportServer 3.0.2. ReportServer 3.0.2 is a maintenance release which fixes several bugs and comes with a few minor improvements. Find a list of all changes in the release notes. Upgrade instructions can be found on the documentations page. We are looking forward to hearing your comments and feedback. Until then …
Happy Reporting
This is the second post in the Dynamic List series and here we dig a bit deeper into the rational behind Dynamic Lists. We discuss data warehouse design and spreadsheets and how the Dynamic List fits into both to then discuss how to optimize your data warehouse design for Dynamic Lists.
ReportServer comes with several reporting engines one being the Dynamic List. While the Dynamic List certainly doesn’t have a flashy name, don’t let that fool you. In simple terms the Dynamic List is The Tool for relational reporting, empowering your users to get the data they need when they need it while at the same time taking the strain from IT as there is hardly any reporting engine out there that is easier to administrate and maintain than Dynamic Lists.
This introduction is the first part of a series of blog posts that look at the Dynamic Lists in greater detail. So far the following posts are available in this series:
ReportServer comes with a flexible authentication mechanism that can be extended via ReportServer’s hookable plugin infrastructure. In the latest addition to our tutorial section we discuss how authentication works behind the scenes and what steps are necessary to extend ReportServer to use your custom authentication scheme.
We hope you find this latest addition useful and are looking forward to hearing your thoughts and comments.
Our latest addition to the tutorials explains how to set up ReportServer in Eclipse. This provides you with the ideal environment to dig deep into ReportServer. Whether you want to really dive into scripting or want to have a poke around ReportServer’s source code, this is the perfect start.