Re: Clarification of simple database terms on Series I

You can create as many indexes as you want over a table, using one or more fields in any order.
It will not affect the programs that use the table, except that for insert or update it will take longer (usualy insignificant, unless you create an absurd amount of indexes) and reads may be much faster if the index helps in the selection or order of the data.

There are several types of index and for some tasks the speed can be unbelivable faster.

A stored procedure is something else, you can write it in SQL, java or any of the ILE languages on i.
It reads data, selects, sums, combines, etc. and returns a result or a result set.

I don't know the SSRS access, if it some kind of client-server it will improve with the index, and using stored procedures you can prepare the data in the server and use the client only for display. Also, you can restrict the access to the procedures and improve the security.

Crystal Reports wrote:

I read where someone speaks of making an index on a field - this means adding it as a key to the table it is in? But would that affect other jobs ? also he refers to creating a Stored Procedure on the AS400. This means a CL prgram? Or there is ability to use something like SQL Server Studio on the AS400 data?

I am not sure if I understand correctly how one accesses the AS400 data perhaps. We are using this data with Microsoft SSRS prgrams.

Thank you,
Paul