SELECT     ctrx_system_perf.instid, ctrx_system_perf.dtperiod, ctrx_system_perf.dtid, ctrx_system_perf.inserted_date,
                      ctrx_system_perf.i1 AS active_sessions_sum, ctrx_system_perf.i2 AS active_sessions_cnt, ctrx_system_perf.i3 AS active_sessions_peak,
                      ctrx_system_perf.i4 AS inactive_sessions_sum, ctrx_system_perf.i5 AS inactive_sessions_cnt, ctrx_system_perf.i6 AS inactive_sessions_peak,
                      ctrx_system_perf.i7 AS total_sessions_sum, ctrx_system_perf.i8 AS total_sessions_cnt, ctrx_system_perf.i9 AS total_sessions_peak,
                      machine.name
FROM         ctrx_system_perf INNER JOIN
                      instance ON ctrx_system_perf.instid = instance.instid INNER JOIN
                      machine ON instance.machid = machine.machid
ORDER BY active_sessions_peak DESC

and check the column that is called “active_sessions_peak” you can see that there will be one or two columns that will have numbers totally out of whack, either much much higher, or much much lower than the rest of the cells in that column. In the past I had a column that had over 10 million active sessions. You can alternatively order by inactive_sessions_peak to see if there are any columns that look incorrect here too. You can change this cell in the query result window to 0 and re run the query and your report should look better.

*This is a bug inside of how edgesight writes to the database. I have do not have info on how edgesight writes data to the table and will not provide support for editing the edgesight tables. Edit at your own risk.

for Example -2147481843 and also -268,432,017.8 within the normal sort of numbers we would expect.

not sure why its displaying this figures,as these are in the middle of the night, when the farm should be quieter.

Average
2011/10/29 – Saturday -2147481843 -2147481933 1571 1511 1478 1465 1471 1484 1500 1519 1540 1550 1550 1529 1505 1472 1472 1451 1433 1404 1400 1365 1367 1343 -178,955,474.8

2011/10/30 – Sunday 1325 1319 1320 1339 1352 1382 1406 1444 1494 1520 1526 1545 1537 1505 1487 1467 1465 1457 1435 1395 1380 1369 1396 1396 1,427.5
2011/10/31 – Monday 1514 -2147481952 1814 1981 2189 2424 2894 3472 3989 4360 -2147478894 4786 4985 5149 5110 5008 4739 4227 3798 3309 3025 2691 2367 -2147481411 -268,432,017.8
2011/11/01 – Tuesday -2147481551 1979 2029 2118 2239 2446 2776 3165 3599 3877 -2147479504 4142 4393 4613 4607 4501 4220 3901 3566 3255 3094 2748 2415 2114 -178,953,719.1
2011/11/02 – Wednesday 2050 -2147481406 2240 2352 2544 -21474

Thanks,
Holger

Thanks for pointing that out, I use a linked server so that I can run cross-database queries to match up some of the Edgesight Data with other data that I have. That was a major oversight.

Also, thank you for your kind comments about my Briforum Session!

Take care Jason

John

I enjoyed your presentation at BriForum!! One note on your hollistic query, you will need to customize the FROM clause to match your environment as the query here references server and instance,

Change
from c3edgesight.citgop_edgesightxa.dbo.vw_es_archive_system_performance
to
from dbo.vw_es_archive_system_performance