running
NT4 SP6
SQL SERVER 7
Baan 4c2

only indexes on current baan sql server tables are the hash fields
using ms-access to create management reports
some tables like tdsls051 has over 1 million rows and it takes 5 - 6 minutes for a query using this to run on the server

we've got a test baan server, and ran the same query after creating a index for a field used in my WHERE clause... it now runs in under 30 secs

I'd like to add indexes on the production server for this and other tables, but am not sure of its impact, if any, on baan ??

We've added additional indexes for that same purpose to Baan tables with no problems. The only problem you would have was if you modified an existing index, but you're only wanting to add which again will not be a problem. Make sure that when you create the new index you check whether it should be a unique or non-unique index. Index1 on all Baan tables are created as unique, and usually all other indexes after the first one tend to be be non-unique. Index1 acts as a primary key. Hope this helps. We use Oracle, but the principles for most relational databases are the same.

Gilbert Guymer
Database Administrator
Lufkin Industries, Inc.

We have created additional indexes when we used to use SQL 7 (and now when we have SQL 2000) and they are fine.