We are on 15.0.3 and our staff is frustrated over the time it takes for the iMIS application to save edits to customer records. Is there anything we can do to speed this up?
Could you share a little more about your environment? Whatever parts you're comfortable sharing would help.
CPU count/speed, RAM, disk arrangement of the SQL and App servers
Location of iMIS app relative to SQL (same server? same LAN? speed of link?)
Version of SQL
Other applications with databases on same SQL server (these are usually OK)
Other windows applications on SQL server or App server
Other websites on app server
Approximate size of your iMIS database (GB)
Approximate number of user defined tables and fields
Any public websites talking to iMIS? Any COM-based iBO involved?
Number of users doing data entry and affected by this
How slow is slow? How long between "Save" and ability to start finding the next record?
In general, you either need a dedicated App server or powerful App server, preferably both. If your App server is both slow and shared, iMIS performance will tend to suffer.
If disk space is below 15% on any server drive, this can dramatically affect performance.
File sharing or Exchange on the same box with SQL or the App server can cause a bottleneck.
Running your iMIS database in Simple recovery mode tends to be slower, but if you switch to Full, make sure you schedule transaction log backups to keep it from growing out of control.
Have your reindexed your iMIS tables lately? SQL can run it automatically at intervals.
Don't schedule a db shrink maintenance plan, or set your database to Autoshrink. This will undo most of the benefit of reindexing.
iMIS 15 uses a number of triggers to synchronize internally. If you have triggers of your own, you might just have too much going on. Consider getting someone who knows a lot about iMIS and SQL in to suggest improvements. The same goes for any stored procedures or large reports that run frequently.
Some general things
Could you share a little more about your environment? Whatever parts you're comfortable sharing would help.
In general, you either need a dedicated App server or powerful App server, preferably both. If your App server is both slow and shared, iMIS performance will tend to suffer.
If disk space is below 15% on any server drive, this can dramatically affect performance.
File sharing or Exchange on the same box with SQL or the App server can cause a bottleneck.
Running your iMIS database in Simple recovery mode tends to be slower, but if you switch to Full, make sure you schedule transaction log backups to keep it from growing out of control.
Have your reindexed your iMIS tables lately? SQL can run it automatically at intervals.
Don't schedule a db shrink maintenance plan, or set your database to Autoshrink. This will undo most of the benefit of reindexing.
iMIS 15 uses a number of triggers to synchronize internally. If you have triggers of your own, you might just have too much going on. Consider getting someone who knows a lot about iMIS and SQL in to suggest improvements. The same goes for any stored procedures or large reports that run frequently.
-- Bruce