|

BAIRS
Reporting
BFS Users Listserve
Budget & GL
Chart of Accounts
Customer Support
Forms
New User Information
News &
Announcements
Obtain a User
ID
Technical Information
Update Chartfields
|
a |
|
BAIRS
Performance Tips

There are several tips, information and reminders we would like to
share with our users running BAIRS reports. These items are
meant
to
enhance
the performance for running your reports. If you have any questions
about them, please call the Budget & Finance User Support (formerly
the BFS/BAIRS) Help Desk at 3-4250.
- Currently, "governing" is turned on in BAIRS
between the hours of 9 AM
and 3:30 PM, Monday through Friday.
During those hours,
any query which
will run for longer than 30 minutes will be prevented from beginning.
Users will receive the following error message if their queries
exceed
30 minutes: Brio.Insight ODS Error-1019: ODS failed to execute
the query
Server Name: GRANITE Message: The SQL Server is
terminating this process. Message Number (5702)
Severity (0). Once a query starts, at 30 minutes elapsed time,
it will move to a lower priority consumer group during the hours
from 7am - 12
midnight. When it's in the lower priority consumer group, it
will run until completion or until 12midnight. Any query will
be prevented from starting that will run longer than 120 minutes
from 7-9am and 3:30pm-12midnight.
This is to ensure
system resources continue to be available to the majority of
users.(If
this is problematic for you, e.g. if you are having
trouble getting the report you need, please call the Budget &
Finance User Support Help
Desk at
3-4250. We can either help you change your parameters so the
report runs
faster or work with you and the technical staff to get you the
data you need.)
- BAIRS is available from 7 AM to Midnight.
Again,
if you are having trouble getting a report you
need during regular hours, please call us rather than kicking off
a large
query before you leave. If everyone on campus ran large queries
at the
day's end, we'd have performance issues until midnight as well.
This may
be an appropriate approach in some circumstances, but there may
be better
approaches available.
- Run summary reports if possible.
If you are looking for the "balances" in your accounts, run a summary
report. Detail reports such as the GL Detail Standard Report are for
exactly that, "detail" transactions. It is advised for reconciliation
to run the GL Transaction Verification Report each month along with
the summary report(s) of your choosing. The GL Transaction Verification
Report contains only those transactions posted to your org codes by
another processing unit and therefore require additional review. Included
in this report might be recharges, new grant/gift appropriations,
and PO's prepared in error by another department using your org code.
If you have questions about the most appropriate reports to run for
the information that you are looking for please call the BFS/BAIRS
Help Desk at 3-4250 or if you have not already done so, enroll in
the Reporting Tools classes.
- Do not ignore Org if at all possible.
In general, reports will run faster if you enter parameter
for org, as opposed to choosing Ignore. A single org code, when possible,
is fastest. But using Org Node to capture all of your department's
data is preferable to selecting Ignore and generates the same results
(for
users with departmental level security). If you are unsure
how to use the Org Node feature on the parameter dashboard, please call
us
at 3-4250.
- The Customer Report ONLY includes revenue & expense
accounts (accounts beginning with 4 or 5).
- If you cancel a query by exiting your browser or pressing
Alt-End, please call the BFS/BAIRS Help Desk at 3-4250 so that
we can cancel
the query from behind the scenes. Canceling a report
or query on your computer often does not cancel it on the database.
Queries which are left running use system resources that other
users need.
Last updated: 11/15/04 |