aball, Member
I just downloaded/installed myDBR just fine for a trial. I'm following the tutorial and it's been hours and I just can't seem to figure out how to add a report!! I created a new "sp_DBR_" function just fine and the documentation says "Click 'Add report' from the main screen's Admin tools" but there's NO "Add Report" in the menu!
Am I missing something here!?
myDBR Team, Key Master
The menu item is called "New report" (we have updated the documentation to use the new term).
When you create a new stored procedure with the prefix sp_DBR (click Execute in SQL Editor so that the routine is created), the SQL Editor shows a button Add report to myDBR. This is the same as clicking the "New report" button in the Admin Tools.
When you click the "New report"-button and you have not yet created a routine, myDBR asks for the routine name and creates a routine skeleton for you. Once you have the routine created and you click the "New report"-button again, myDBR offers to create a report based on the created routine.
--
myDBR Team
aball, Member
OK, I followed your exact steps and yes, that works, but sorry to say this is very un-intuitive. There should be an "Add report" button on the main menu that allows you to select an sp_DBR to create a report against. What happened with me is that I tried to create the sp_DBR through the "New report" button and got very confused on what to do so I used an external SQL editor to create the sp_DBR but then got stuck on what to do next. Allowing the user freedom to create the sp_DBR in an external editor and then "Adding" the report using the "Add report" button would be much better frankly.
Also, I'm again stuck since myDBR doesn't want to run the sp_DBR function created against the data database and keeps insisting on running it against the myDBR database. How do I fix that?
Thank you..
aball, Member
OK, I think I figured-it-out.. I had to use the 'mydatabase..mytable' convention to tell myDBR which tables to read from and the sp_DBR function is actually stored in the myDBR database NOT the user report database.
It's a bit of a learning curve but slowly understanding how this system works.
myDBR Team, Key Master
When you create a report into myDBR two things need to be done.
When you first click the 'Add report'-button, myDBR asks for the procedure name and creates a skeleton for the procedure. Once you have created the procedure in SQL Editor, myDBR will bring up a button 'Add report to myDBR' directly in the SQL Editor.
If you click the 'Add report'-button when you already have report routines that have not yet been attached as reports, myDBR will offer for you to do that.
Allowing the user freedom to create the sp_DBR in an external editor and then "Adding" the report using the "Add report" button would be much better frankly.
myDBR reports are normal native stored procedures. You have absolutely the freedom to use any external editor to create/edit the reports. In many environments, direct access to the database is prohibited. If you have an access with an external editor and prefer to use it, feel free to do so.
myDBR's SQL Editor offers some quick tools for you when you create the reports. Try highlighting an object (routine, function, table, view, or a myDBR command) and click the 'Show selected object' button).
OK, I think I figured-it-out.. I had to use the 'mydatabase..mytable' convention to tell myDBR which tables to read from and the sp_DBR function is actually stored in the myDBR database NOT the user report database.
The SQL you write is standard SQL, not myDBR specific one. If you installed (the default) myDBR into its own database use the syntax database.[schema].table in SQL Server and in Sybase and database.table in MySQL/MariaDB.
You can also install myDBR into the same database as your data (myDBR has its own naming scheme so it will try not to conflict with your tables/routines), but by default, it is installed into its own database.
--
myDBR Team
aball, Member
Thank you for the clear explanation.. I still believe it is more intuitive to have an "Add report" button on the main menu..
Nonetheless, after I got a few reports created I'm thoroughly impressed by myDBR and see how powerful this product is. I'd like to buy a license but a bit confused on what to fill-out for "HOST". I'm running the application on a dedicated PHP server (call it php_server) and it's reading data from the main SQL database server (call it sql_server) and I have a port forward to php_server on the router to access the reports from outside the LAN. I'm guessing I need to fill-out "sql_server" for "HOST", is that correct?
myDBR Team, Key Master
The host is the hostname of the server hosting the myDBR installation. When you access myDBR with the browser, you have an URL like:
https://yourserver.com/mydbr/index.php
The HOST asked by the myDBR Shop is the yourserver.com
--
myDBR Team
aball, Member
Thank you, I just purchased a license.. now I'm faced with a simple dilemma. I used our DDNS for host since sometimes these reports will be access from outside the LAN but when I'm working on development accessing myDBR through the local LAN address is much faster of course. I tried access through the LAN address but as suspected myDBR thinks I don't have a valid license. Anyway to work around this without having to buy another license for what is practically the same "domain"?
myDBR Team, Key Master
myDBR is licensed per installation and the installation is checked against the hostname. Would advise to consider right balance for you.
--
myDBR Team
aball, Member
Thank you, but I don't understand what you meant by "Would advise to consider right balance for you". It's the same installation just arriving to the server in two different routes: One through the WAN and the other through the LAN, but they are the same server.
myDBR Team, Key Master
The license is bound to the hostname. You need to decide using which hostname you wish to access it. If you want to use multiple hostnames, it is treated as a separate installation (myDBR does not know if it is a separate or the same one).
--
myDBR Team
You must log in to post.