I have been having an issue with slowness involved with calling the Save() method on a CContact object using iBO for .NET.  When saving a CContact object, it consistantly takes 8-12 seconds to complete. We have a rather large database (over 600,000 records in the Name table), and it seems that the issue lies within the asi_Name_Insert_Update trigger, more specifically the asi_FixDuplicateIndividualRows stored procedure that runs when the MEMBER_TYPE, COMPANY_RECORD, or MEMBER_RECORD columns are edited.

Hi people.

In 10.6  our users run an ADHOC query to identify which records they have touched during the day to produce labels to post out their results..

In this case the Name_Results_Summary  table where their username is entered into the table in the updated_by field.

Here is the username element fo the adhoc..

Name_Results_Summary.UPDATED_BY = Substring(user_name(),1,Case when charindex('_',user_name()) > 0 Then charindex('_',user_name())-1 Else len(user_name())End )

Just updating and re-emphasizing a previous blog post about refreshing view metadata (see previous blog post).

Future iMIS Database Upgrades will validate all view metadata by running the script in my previous Blog entry on the subject (reproduced below).  Therefore, it's vitally important that all existing iMIS users run this script against their databases prior to upgrading to the next major version of iMIS in order to avoid errors during the database upgrade.

When database schema changes, as it often does during upgrades or customizations, any existing views refering to that schema remain unaltered.  For example, if a UserId field is lengthened from 30 to 60 characters in the schema, any view referencing that field will remain at 30 characters.  The solution to this, short of editing all the views, is to call sp_refreshview on the view.

The following is a little script that can be run on your database.  It will refresh the views for all schema objects in the 'dbo' schema (which includes all IMIS tables).  If you have a lot of tables in your database that exist in other schemas, you may wish to eliminate the clause that limits the script to only 'dbo', in order to ensure everything is refreshed and up to date.  This can be run at any time, and it is completely non-destructive.  If this script throws any errors, it's likely due to the existence of old obsolete views that reference schema that has either been renamed or dropped... you'll have to manually fix such issues by either fixing or dropping the offending view.

It is getting progressively harder to find older copies of application software.  Can anyone tell me if it is possible to use SQL Server 2005 with iMIS and eSeries version 10.5.28.02?
 

I am looking for information in the PHP toolkit that Marty talked about during Innovations... is anything posted here?

Posted this issue in the blog but though it might fit well here in the Forum.

Problem
I initially logged the issue we were having working with the latest 15.1 release. The issues presented itself when using an existing DB and upgrading in a test environment. Installing with a demo database worked fine but using a 15.0 DB and upgrading presented this .net error trying to load the web view (Shown below). The error indicated it could not find the site map node. This turned out to be misleading. After many installs and re-installs on both a demo and upgrade I resolved the issue.

The way user logins are handled and stored has changed in iMIS 15.1

In this new version of iMIS, all your users (logins in the Name_Security table) will have matching records in the UserMain table. Importing all these users into UserMain can have a snag though: it's possible for there to be the same login ID in Name_Security as one already specified in UserMain. That is, two separate logins could exist with the same login id. This is no longer the case.

There are several problems that have been becoming more prevalent with iMIS 10.x.NET and iMIS15 involving various security and connection issues. Below, is a list of common issues and solutions:

• 13: Type Mismatch Error when trying to log in through the desktop
• The login account 'sa' has been locked out
• The webpage is unavailable

These are becoming more common errors and are caused by several different possible problems:

The following SQL script can be run on any 10.6 database to validate that some specific, common data problems that would interfere with a smooth upgrade to 15.x are not present. If any issues are present, they are displayed. If you run this from SQL Query Analyzer or SQL Server Management Studio, set the "results to text" option before running this script, for the best display of the results.