Oracle2SSRS

This is the report file this tool wrote for you — an RDL (Report Definition Language) file, the format SSRS reads. It is the thing you download and upload to the server. You do not have to read it; it is here so you can check anything you want to check. A very long file shows only its beginning here, but every download contains the whole file.

A sub-report is a second report that a row in the main report opens — the envelope for one permit, say, or the detail behind one line. Build one from whatever you have: its Oracle XML, an existing .rdl, or just its SQL (.sql, .docx or .txt). Drop the files onto a card below, or into the Sub-reports box in the panel on the left, then click Build & preview. You get a full report file and a preview, the same way you do for the main report.

The Oracle file you dropped in is on the left; the SSRS file this tool wrote is on the right. Search both sides for a column or query name when you need to answer “where did this end up?” — for yourself, or for whoever asks how a number got onto the page.

Everything this tool checked before you deploy. Each finding says what will happen when the report runs, and what to do about it. Four words are used, most urgent first: BLOCKER — the file will not upload or open cleanly; fix this first. RED — it uploads, but something is likely to go wrong once the report runs. AMBER — worth reading; the report should still run. READY — nothing is standing in your way.

The steps for putting this report on your server, in order. Steps marked Done for you are already handled inside the file you download — they are listed so you can see what was done. Steps marked You do this, Needs finishing or Take care need a person.

How much of the original report came across, and a record of the decisions this tool made while converting.