How to determine a bad BAQ

Yahoo Archive
1
Blake,

How many folks are writing reports/BAQ's at your organization? Who has created these allegedly faulty BAQs? I.T. should be writing reports and responsible for the results. By IT, I mean one or two people max.

How many custom BAQs do you have approximately? 10? 20? 100? Run the more popular ones (view History in the System Agent) and see if you can duplicate the problem. Keep a log and have users email you when they experience these performance issues. Analyze this log and see if you find patterns. Cross reference with your server.log files and see if you find anything.

Someone mentioned TEST servers.... I do that as normal protocol. That's a necessary thing and a great recommendation. Never deploy a new or modified BAQ unknowingly on a LIVE server (or worst case, not during normal business hrs).

If you are SQL, your TEMP database will inflate faster than Bubble Boy's balloon. That's a clear indication of a malformed BAQ.

Good luck.


Vic


Vic Drecchio
ERP Administrator
TIMCO Aviation Services
Greensboro, NC
Email:Â Â vic.drecchio@...
Mobile:Â 704.530.3092

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Blake Clemens
Sent: Tuesday, December 01, 2009 12:39 PM
To: vantage@yahoogroups.com
Subject: [Vantage] How to determine a bad BAQ

We've been having system performance issues with Vantage from day one.
Now we're being told that our issues are most likely stemming from a
poorly written BAQ/Report. We have to locate the this report and fix
the problem. Sounds easy enough. My question is what makes a
BAQ/Report bad? How do we determine which BAQ/Report? All our
BAQ/reports run without issues and at times run very well. So if there
isn't an obvious indication that something is wrong with the BAQ/Report
how do I determine what makes one bad??



Thanks,

Blake Clemens

IT Systems Engineer

Delmarva Millwork Corporation

(800) 360-2364 x132



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



------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
2
We've been having system performance issues with Vantage from day one.
Now we're being told that our issues are most likely stemming from a
poorly written BAQ/Report. We have to locate the this report and fix
the problem. Sounds easy enough. My question is what makes a
BAQ/Report bad? How do we determine which BAQ/Report? All our
BAQ/reports run without issues and at times run very well. So if there
isn't an obvious indication that something is wrong with the BAQ/Report
how do I determine what makes one bad??



Thanks,

Blake Clemens

IT Systems Engineer

Delmarva Millwork Corporation

(800) 360-2364 x132



[Non-text portions of this message have been removed]
3
If you are on SQL you could run a trace to locate the bad query.



If you are on progress I would run the promon tool to make sure you aren't
having poor DB performance. But there isn't really a tool to pinpoint a bad
query that is running.



~Charlie

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Blake Clemens
Sent: Tuesday, December 01, 2009 12:39 PM
To: vantage@yahoogroups.com
Subject: [Vantage] How to determine a bad BAQ





We've been having system performance issues with Vantage from day one.
Now we're being told that our issues are most likely stemming from a
poorly written BAQ/Report. We have to locate the this report and fix
the problem. Sounds easy enough. My question is what makes a
BAQ/Report bad? How do we determine which BAQ/Report? All our
BAQ/reports run without issues and at times run very well. So if there
isn't an obvious indication that something is wrong with the BAQ/Report
how do I determine what makes one bad??

Thanks,

Blake Clemens

IT Systems Engineer

Delmarva Millwork Corporation

(800) 360-2364 x132

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





[Non-text portions of this message have been removed]
4
Lemme throw a perspectives plug in here. In the Sys Ad class, Ben Nixon
said that you create the new BAQ on a test server. Then open your task
manager, and monitor the CPU usage, and the memory usage when you run
that BAQ. You can also monitor your temp folder (/mfgwrk803) for large
DBI files that get created. If your CPU pegs at 100, a very large DBI
file is generated, and your memory takes a hit, then the BAQ is probably
something that you wouldn't wanna run in your live environment.







From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Blake Clemens
Sent: Tuesday, December 01, 2009 11:39 AM
To: vantage@yahoogroups.com
Subject: [Vantage] How to determine a bad BAQ





We've been having system performance issues with Vantage from day one.
Now we're being told that our issues are most likely stemming from a
poorly written BAQ/Report. We have to locate the this report and fix
the problem. Sounds easy enough. My question is what makes a
BAQ/Report bad? How do we determine which BAQ/Report? All our
BAQ/reports run without issues and at times run very well. So if there
isn't an obvious indication that something is wrong with the BAQ/Report
how do I determine what makes one bad??

Thanks,

Blake Clemens

IT Systems Engineer

Delmarva Millwork Corporation

(800) 360-2364 x132

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





[Non-text portions of this message have been removed]
5
Also from Perspectives, Mark Pladson had an excellent session on Best Practices for BAQs. There he mentioned if you have a runaway BAQ, you can check your server log and look for a "...long running BAQ..." error with PID of the offending user. It's worth a quick look to see if your server logs give you any clues.



--- In vantage@yahoogroups.com, "Blake Clemens" <blake.clemens@...> wrote:
>
> We've been having system performance issues with Vantage from day one.
> Now we're being told that our issues are most likely stemming from a
> poorly written BAQ/Report. We have to locate the this report and fix
> the problem. Sounds easy enough. My question is what makes a
> BAQ/Report bad? How do we determine which BAQ/Report? All our
> BAQ/reports run without issues and at times run very well. So if there
> isn't an obvious indication that something is wrong with the BAQ/Report
> how do I determine what makes one bad??
>
>
>
> Thanks,
>
> Blake Clemens
>
> IT Systems Engineer
>
> Delmarva Millwork Corporation
>
> (800) 360-2364 x132
>
>
>
> [Non-text portions of this message have been removed]
>
6
Ditto on Ben Nixon's advice. Are you on Progress or SQL? We're on SQL and rebuilding the indexes helped with performance. The name of the game with Vantage is Disk I/O so don't skimp on that subsystem. It's basically not possible to throw too much hardware at Vantage. There really is no hard rule to determine a bad BAQ. Basically a bad BAQ is one that brings the system to its knees, so test before deploying.
Jared
_______________________
Jared Allmond
IT Systems Administrator
Wright Coating Technologies
jallmond@...<mailto:jallmond@...>
voice: 269.344.8195
direct: 269.341.4353
fax: 269.344.3007



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