Indexing

[Morley]

Indexing appears not to be automatic when relationships are created. How is indexing turned on? Where can one get feedback on what's indexed and what's not?

[jcompagner]

not yet.. Will be in further version >2

[Westy]

You can put an index on a field using Sybase Central. Depending on your solution you may not need indexing. With the Firebird database I found that with tables of 20,000 records I did not need indexing, and Sybase appears to be significantly faster than Firebird. It really depends on what you are trying to do. However, just because you may have needed indexing when developing with another platform, do not assume that you will need it with Servoy.

[Morley]

You can put an index on a field using Sybase Central. Depending on your solution you may not need indexing. With the Firebird database I found that with tables of 20,000 records I did not need indexing, and Sybase appears to be significantly faster than Firebird. It really depends on what you are trying to do. However, just because you may have needed indexing when developing with another platform, do not assume that you will need it with Servoy.

In FileMaker Pro we're used to indexing for foreign keys, haven't turned on indexing for much else.

You're saying Indexing is no longer strictly required, is much more for performance issues. Interesting.

[bcusick]

Indexing appears not to be automatic when relationships are created. How is indexing turned on? Where can one get feedback on what's indexed and what's not?

The world of SQL is VERY different than the world of FileMaker!

In SQL if you index a column - it can be SLOWER than a non-indexed field. GENERAL RULE: If you have less than 50,000 to 100,000 records - NO NEED TO INDEX.

Cheers,

Bob Cusick

[Morley]

Indexing appears not to be automatic when relationships are created. How is indexing turned on? Where can one get feedback on what's indexed and what's not?

The world of SQL is VERY different than the world of FileMaker!

In SQL if you index a column - it can be SLOWER than a non-indexed field. GENERAL RULE: If you have less than 50,000 to 100,000 records - NO NEED TO INDEX.

Cheers,

Bob Cusick

If indexing isn't mandatory, why index at all then? I'm startled at the concept of indexing reducing speed. I well remember the speedy days of FMP1 and 2 when ALL fields were indexed and FMP ran like lightning.

Also, is it possible in Servoy to automatically turn indexing on or off when record count exceeds or reduces to a particular record count?

[maarten]

If you're new to SQL, here's a good link to get you started.
IT will give you a general basic knowledge about SQL
http://members.tripod.com/er4ebus/sql/
This chapter specifically discusses indexing.
http://members.tripod.com/er4ebus/sql/ch10.htm

[jcompagner]

indexing is something for the database, not servoy.

Some databases auto index FK columns.. (thats how they maintain integrity) others don't.

Especially for string (like) searches indexen can help.

Some database do it on demand (they look what you are doing and make an index for you)

Just look how youre database works, and look what columns you search on in youre big queries and make an index on those)

index can reduce speed on updates and insertes, because besides the record itself it also needs to update the index.

Many databases have tools where you can learn what queries are costing and how they are looked up internally in the database. This way you can learn to make youre index. (avoid full tablescans)