Eric_Bisto

Hello all, Been looking at BYOD, got quotes from all the big players, Xirrus, Meru (RM), Ruckus, and AirTight. AirTight comes in quite a bit cheaper than the others, the cloud management looks really pretty decent - just wondering if any of you guys have it installed and are using it in a real environment. I like the Meru product, the presentation from RM was very slick and I have the confidence that it will just work, but the cost is out of this world.... 10K over the Airtight quote for the same coverage. So, that's why i'm asking. What's it like in the real world?

Thanks Glennda, I have indeed reported this case to Capita, but they haven't responded, I'm not really sure what's going on with them at the moment because we have another outstanding issue with SLG users not being provisioned (which, appears not to be just us as another school in the next town has the same problem) but normally they respond the same or next day, this call has been open a week with no further contact. I don't have high hopes for this one, either sadly (i reported it yesterday)

Now the new term is in full swing i've been getting reports that SIMS.NET the client is quite slow, which I am seeing for myself. Some screens load quickly, others take a noticeably long time to appear. I've been doing some monitoring on the server using perfmon and SQL profiler and my investigation seems to identify the culprit to be the "sims.itc_pix_MyMessagesWidget_Load" stored procedure. The average execution time of the query is around 2500-3000 milliseconds, but what i think is causing the excessive load on the sql engine is the number of reads required for the operation which range from about 250,000 to over 600,000 - this number is (hundreds of) thousands times more than what i'm seeing as an average for most other operations, only a few seem comparable and this procedure seems to be executed on the server every few seconds by all the users who happen to have SIMS open and it's executed by any given user about every 60-90 seconds, give or take. This operation stands out like a sore thumb because many other operations occur with less than 50 reads and with significantly less cpu time. It just looks like the number of users using SIMS, leaving it open with the background checking of messages is killing the server. I see other stored procedures taking lots of cpu time and requiring many reads, such as sims.sta_pix_BehaviourSummary_Load and sims.sta_pix_AchievementSummary_Load, but these occur significantly less frequently and appear user initiated, sims.itc_pix_MyMessagesWidget_Load just seems to gobble cpu cycles and disk in the background. by any stretch, an operation which happens every few seconds requiring 600,000 reads seems abnormal, especially for something as simple as updating a message widget. This seems to be something which changed in the Summer update as we didn't have this last year. Any other intouch users finding this?