Upgraded from 2.13 to 4.02.1 and SLOW on MSSQL 7

[scad...@my-deja.com]

We upgraded 100 users from SLGX 2.13/MSSQL 6.5 to SLGX 4.02.1/MSSQL 7
sp1. 20 users were configed to have read only rights in SLGX
frontend. Overall performance has degraded since going to 4.02.1.
We've seen locking in MSSQL 7.

I have seen a read only user that says they were clicking on the
contacts or opportunities navbar and performing lookups causing the
locks. I am trying to run the profiler and view the queries when
clicking on the navbar and searching.

I have seen massive select all type queries with an inner join on
contact, address, and or opportunities.

Anyone seen similar or have the magic cure?

Thanks!

Steve Cadigan

Sent via Deja.com http://www.deja.com/
Before you buy.

[steve_v...@my-deja.com]

We are on SLX 3.016 using SQL 7.0 sp1. WE are on a Pention III Quad
processor 2 gig memory server with 40 Workgroup and 45 remotes. WE see
SQL locks occassionally. They are even caused by people who are doing
nothing in SLX at the time. We just have them F5 to refresh and lock
is cleared. It seems strange.
Ohh and never cut a remote database during the day. It will lock
everyone up!

In article <8ms2km$upr$1...@nnrp1.deja.com>,

[mea...@my-deja.com]

The locks you are getting while people are doing nothing is probably
related to a group they have open in SalesLogix.
Make sure you do not have any groups that a lot of people are working
on at the same time.

For the select all groups you are running into, make sure that you do
not have the "All accounts" or "Recent Accounts" groups bringing back
too many records.
SalesLogix ships with groups that attempt to bring back everyone in the
database (apparently they plan on people having less than 1/4 million
contacts in their database).

If this checks out, be sure that you have optimized all of your indexes
on your database.
I hjave mentioned it before, but the lack of a join on the type field
and the date fields on the history table causes the default
configuration of SalesLogix to do a table scan every time it opens.

MSSQL 7 ships with some database analysis tools that will allow you to
take a snapshot of some activity.
I was amazed at the indexing errors and inefficiencies I found when I
ran them on my database.
Read the instructions in the books online for the MS SQL 7 profiler if
you do not know how to do this already.

In article <8ms5ht$11a$1...@nnrp1.deja.com>,