{Disarmed} RE: Ability to create a BAQ

Yahoo Archive
1
The SDK would be an alternative.



Personally I feel the best option would be to provide an "Advanced" BAQ
editor,

Such that one could free enter the 4GL code - handling any optimization
that is required.



You could then utilize the BAQ framework for Dashboards and reports

But have the flexibility of creating the temp-table, calculated fields
etc.



Or provide the ability to include a BAQ inside an existing baq, its
frustratingly

Difficult to use - I mean you cant even have OrderHed -> Customer
(soldTo) and Customer for (BillTo)

Things like providing aliases for Table names so you can add them more
than once.

Things like timed execution and statistics would be a bonus.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Rojas, Joe
Sent: 17 April 2008 13:39
To: vantage@yahoogroups.com
Subject: RE: {Disarmed} RE: [Vantage] Ability to create a BAQ...



I agree.

Is there another alternative to BAQs other than ODBC?

Joe Rojas

Information Technology Manager

Symmetry Medical New Bedford

P: 508.998.4575

C:508.838.4717

joe.rojas@... <mailto:joe.rojas%40symmetrynb.com>
<mailto:joe.rojas@... <mailto:joe.rojas%40symmetrynb.com> >

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
Of Robert Brown
Sent: Wednesday, April 16, 2008 9:02 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: {Disarmed} RE: [Vantage] Ability to create a BAQ...

The problem is that epicor offers no direct edit mechanism (like a
simple sql test editor) that allows the author of the BAQ to optimize
the code. The phrase builder does no optimization and, like sql, the
order of joins and critiria can have a HUGE impact on performance.

I used better db query tools in the 80s. Epicor not only makes
themselves look bad, they make a decent db like Progress look bad.

Rob Brown

Thomas Rose <t.rose@...
<mailto:t.rose%40electricmirror.com>
<mailto:t.rose%40electricmirror.com> > wrote:

While on this subject, do you have any suggestions on how to avoid these
apparently cumbersome BAQ's? It seems to me that in order to get certain
data out, some BAQ's will be fairly complex. Is it the complexity of the
BAQ that causes the problem, is it the number of records that are
returned, or is there some other factor that causes a BAQ to tie up the
system?

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> ] On
Behalf Of Charles Carden
Sent: Wednesday, April 16, 2008 2:52 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: {Disarmed} RE: [Vantage] Ability to create a BAQ...

I don't allow anyone access to BAQ on the live server. I have had the
same
experiences as you where users will lock up a machine or at the very
least;
eat up most of its processing power. I have a couple of people who can
create them on the test server and once I have confirmed they work okay
then
I will import them to the live. In fact, I even create mine on the test
server. Although I may have written thousands of queries I can still get
interrupted and miss something obvious. Of course, my test and live
environments reside on different physical machines so that works well. I
transfer my live database to the test server every weekend so everyone
is
still looking at recent data on the test. I can always take down the
test
server if something happens.

_____

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>]
On Behalf Of
jplehr
Sent: Wednesday, April 16, 2008 4:19 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Ability to create a BAQ...

How do others handle who has access to create a BAQ? I have always
controlled this myself. Years back I remember taking my Server down
because I wasn't real sure on what I was doing. I have even seen those
who thought they knew what they were doing slow a Server down
considerably. I am in a much larger organization now and beginning to
receive more requests.

All thoughts are appreciated.

[Non-text portions of this message have been removed]

---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try
it now.

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]
2
How do others handle who has access to create a BAQ? I have always
controlled this myself. Years back I remember taking my Server down
because I wasn't real sure on what I was doing. I have even seen those
who thought they knew what they were doing slow a Server down
considerably. I am in a much larger organization now and beginning to
receive more requests.

All thoughts are appreciated.
3
I don't allow anyone access to BAQ on the live server. I have had the same
experiences as you where users will lock up a machine or at the very least;
eat up most of its processing power. I have a couple of people who can
create them on the test server and once I have confirmed they work okay then
I will import them to the live. In fact, I even create mine on the test
server. Although I may have written thousands of queries I can still get
interrupted and miss something obvious. Of course, my test and live
environments reside on different physical machines so that works well. I
transfer my live database to the test server every weekend so everyone is
still looking at recent data on the test. I can always take down the test
server if something happens.



_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
jplehr
Sent: Wednesday, April 16, 2008 4:19 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Ability to create a BAQ...



How do others handle who has access to create a BAQ? I have always
controlled this myself. Years back I remember taking my Server down
because I wasn't real sure on what I was doing. I have even seen those
who thought they knew what they were doing slow a Server down
considerably. I am in a much larger organization now and beginning to
receive more requests.

All thoughts are appreciated.





[Non-text portions of this message have been removed]
4
While on this subject, do you have any suggestions on how to avoid these apparently cumbersome BAQ's? It seems to me that in order to get certain data out, some BAQ's will be fairly complex. Is it the complexity of the BAQ that causes the problem, is it the number of records that are returned, or is there some other factor that causes a BAQ to tie up the system?

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Charles Carden
Sent: Wednesday, April 16, 2008 2:52 PM
To: vantage@yahoogroups.com
Subject: {Disarmed} RE: [Vantage] Ability to create a BAQ...


I don't allow anyone access to BAQ on the live server. I have had the same
experiences as you where users will lock up a machine or at the very least;
eat up most of its processing power. I have a couple of people who can
create them on the test server and once I have confirmed they work okay then
I will import them to the live. In fact, I even create mine on the test
server. Although I may have written thousands of queries I can still get
interrupted and miss something obvious. Of course, my test and live
environments reside on different physical machines so that works well. I
transfer my live database to the test server every weekend so everyone is
still looking at recent data on the test. I can always take down the test
server if something happens.

_____

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of
jplehr
Sent: Wednesday, April 16, 2008 4:19 PM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Ability to create a BAQ...

How do others handle who has access to create a BAQ? I have always
controlled this myself. Years back I remember taking my Server down
because I wasn't real sure on what I was doing. I have even seen those
who thought they knew what they were doing slow a Server down
considerably. I am in a much larger organization now and beginning to
receive more requests.

All thoughts are appreciated.




[Non-text portions of this message have been removed]
5
I have written some pretty complex BAQ's in the last year or so. Some of
them use 10 or more tables with many criteria statements. In the early
versions of 8.0, BAQ was totally unusable as they would either take forever
or not finish at all. Since upgrading to 8.03.305 that problem seems to
have been resolved. I can't remember the last time I had a BAQ lock up on
me or take longer than a few minutes to run. If I watch my joins the
queries will usually run quickly. I always try to create my joins using
existing indexes unless I simply cannot get the correct data; then I have to
resort to other means. My biggest complaints about BAQ are its lack of
support for null date fields and summary queries. A null date is not less
that 01/01/2007 and that first/last selection just does not produce the
results I would expect. I have had to resort to ODBC reports at times which
have their own set of problems, especially in 8.03.403 and above. Of course,
I always try to estimate how many rows will be returned in a query and if I
feel like it is going to be too big to handle or won't fit in an Excel
spreadsheet then I make provisions to limit it. I would estimate that 95%
of the request that I get are for queries and/or reports that can be
exported to Excel. That automatically places limits on the number of rows
that can be returned.



I would definitely try a BAQ before resorting to ODBC. The BAQ reports are
really quite easy to create and even the prompt screens can be customized to
provide explanations for the options and filters. A dashboard on top of a
BAQ is also pretty handy; however, the filtering can be difficult to obtain
because of the lack of parenthesis in the Filter panel.





_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Thomas Rose
Sent: Wednesday, April 16, 2008 5:34 PM
To: vantage@yahoogroups.com
Subject: RE: {Disarmed} RE: [Vantage] Ability to create a BAQ...




While on this subject, do you have any suggestions on how to avoid these
apparently cumbersome BAQ's? It seems to me that in order to get certain
data out, some BAQ's will be fairly complex. Is it the complexity of the BAQ
that causes the problem, is it the number of records that are returned, or
is there some other factor that causes a BAQ to tie up the system?

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com] On
Behalf Of Charles Carden
Sent: Wednesday, April 16, 2008 2:52 PM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Subject: {Disarmed} RE: [Vantage] Ability to create a BAQ...

I don't allow anyone access to BAQ on the live server. I have had the same
experiences as you where users will lock up a machine or at the very least;
eat up most of its processing power. I have a couple of people who can
create them on the test server and once I have confirmed they work okay then
I will import them to the live. In fact, I even create mine on the test
server. Although I may have written thousands of queries I can still get
interrupted and miss something obvious. Of course, my test and live
environments reside on different physical machines so that works well. I
transfer my live database to the test server every weekend so everyone is
still looking at recent data on the test. I can always take down the test
server if something happens.

_____

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com>
.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups
<mailto:vantage%40yahoogroups.com> .com<mailto:vantage%40yahoogroups.com>]
On Behalf Of
jplehr
Sent: Wednesday, April 16, 2008 4:19 PM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com>
.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Ability to create a BAQ...

How do others handle who has access to create a BAQ? I have always
controlled this myself. Years back I remember taking my Server down
because I wasn't real sure on what I was doing. I have even seen those
who thought they knew what they were doing slow a Server down
considerably. I am in a much larger organization now and beginning to
receive more requests.

All thoughts are appreciated.

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
6
The problem is that epicor offers no direct edit mechanism (like a simple sql test editor) that allows the author of the BAQ to optimize the code. The phrase builder does no optimization and, like sql, the order of joins and critiria can have a HUGE impact on performance.

I used better db query tools in the 80s. Epicor not only makes themselves look bad, they make a decent db like Progress look bad.

Rob Brown



Thomas Rose <t.rose@...> wrote:

While on this subject, do you have any suggestions on how to avoid these apparently cumbersome BAQ's? It seems to me that in order to get certain data out, some BAQ's will be fairly complex. Is it the complexity of the BAQ that causes the problem, is it the number of records that are returned, or is there some other factor that causes a BAQ to tie up the system?

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Charles Carden
Sent: Wednesday, April 16, 2008 2:52 PM
To: vantage@yahoogroups.com
Subject: {Disarmed} RE: [Vantage] Ability to create a BAQ...

I don't allow anyone access to BAQ on the live server. I have had the same
experiences as you where users will lock up a machine or at the very least;
eat up most of its processing power. I have a couple of people who can
create them on the test server and once I have confirmed they work okay then
I will import them to the live. In fact, I even create mine on the test
server. Although I may have written thousands of queries I can still get
interrupted and miss something obvious. Of course, my test and live
environments reside on different physical machines so that works well. I
transfer my live database to the test server every weekend so everyone is
still looking at recent data on the test. I can always take down the test
server if something happens.

_____

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of
jplehr
Sent: Wednesday, April 16, 2008 4:19 PM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Ability to create a BAQ...

How do others handle who has access to create a BAQ? I have always
controlled this myself. Years back I remember taking my Server down
because I wasn't real sure on what I was doing. I have even seen those
who thought they knew what they were doing slow a Server down
considerably. I am in a much larger organization now and beginning to
receive more requests.

All thoughts are appreciated.

[Non-text portions of this message have been removed]






---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

[Non-text portions of this message have been removed]
7
I agree.

Is there another alternative to BAQs other than ODBC?



Joe Rojas

Information Technology Manager

Symmetry Medical New Bedford

P: 508.998.4575

C:508.838.4717

joe.rojas@... <mailto:joe.rojas@...>



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Robert Brown
Sent: Wednesday, April 16, 2008 9:02 PM
To: vantage@yahoogroups.com
Subject: RE: {Disarmed} RE: [Vantage] Ability to create a BAQ...



The problem is that epicor offers no direct edit mechanism (like a
simple sql test editor) that allows the author of the BAQ to optimize
the code. The phrase builder does no optimization and, like sql, the
order of joins and critiria can have a HUGE impact on performance.

I used better db query tools in the 80s. Epicor not only makes
themselves look bad, they make a decent db like Progress look bad.

Rob Brown



Thomas Rose <t.rose@...
<mailto:t.rose%40electricmirror.com> > wrote:

While on this subject, do you have any suggestions on how to avoid these
apparently cumbersome BAQ's? It seems to me that in order to get certain
data out, some BAQ's will be fairly complex. Is it the complexity of the
BAQ that causes the problem, is it the number of records that are
returned, or is there some other factor that causes a BAQ to tie up the
system?

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of Charles Carden
Sent: Wednesday, April 16, 2008 2:52 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: {Disarmed} RE: [Vantage] Ability to create a BAQ...

I don't allow anyone access to BAQ on the live server. I have had the
same
experiences as you where users will lock up a machine or at the very
least;
eat up most of its processing power. I have a couple of people who can
create them on the test server and once I have confirmed they work okay
then
I will import them to the live. In fact, I even create mine on the test
server. Although I may have written thousands of queries I can still get
interrupted and miss something obvious. Of course, my test and live
environments reside on different physical machines so that works well. I
transfer my live database to the test server every weekend so everyone
is
still looking at recent data on the test. I can always take down the
test
server if something happens.

_____

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>]
On Behalf Of
jplehr
Sent: Wednesday, April 16, 2008 4:19 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Ability to create a BAQ...

How do others handle who has access to create a BAQ? I have always
controlled this myself. Years back I remember taking my Server down
because I wasn't real sure on what I was doing. I have even seen those
who thought they knew what they were doing slow a Server down
considerably. I am in a much larger organization now and beginning to
receive more requests.

All thoughts are appreciated.

[Non-text portions of this message have been removed]

---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try
it now.

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]