Tablespaces?
I thought Remedy only uses one Tablespace namely 'ARSYSTEM'?
Or am I misunderstanding the question? :-p

By default, there are at minimum 3 tablespaces which are very often used by AR System :
* ARSYSTEM
* TEMP
* UNDO

You should ensure you that there are on seperate disks and the TEMP tablespace is on the fastest disks.

You can also have multiple datafile per tablespace which are splitted onto different disks....

You have the possibility to add more tablespaces for AR System data and indexes. For example :
* ARSYS_DATA1
* ARSYS_IDX1
* ARSYS_DATA_ARCH1
* ARSYS_IDX_ARCH1

It's just an example... For some AR System application I had developped we have 16 tablespaces for AR System data and indexes...

Then you can move tables and indexes (using my Advanced Admin Tool which is available in the download section ) or use ardb.conf file to create new objects on the good tablespace or do both : Move objects with the AAT and generate the ardb.conf file with perl script which is available on cummunity site.

Cool, Didn't know you could do that.
Ok so TEMP Tablespace is always used by Remedy? I thought it is only used for installation?

But in the case of putting the Service Desk on a different Tablespace, shouldn't you create the ardb.conf prior to installing the Service Desk?

I assume this wont work:
Form: B123C53680001
Clause:TABLESPACE SectionA
Field {
id:53680001
Clause: NOT FOR REPLICATION
}

No, TEMP tablespace is used by AR System and very often. This is why you need in general a big TEMP tablespace specially if you have a lot of join forms and/or unqualified searches.

Look at the Optimizing and Troubleshooting guide for more complete information.

For ITSM 7 a good value for very small databases (<30GB) can be 1GB...

The form names in ardb.conf should exist within arschema right?

It's impossible for the first installation because you don't know all forms, fields and indexes before installing it...

This is why I had developped the AAT and this tool is in production on many of my customer's site...

If you want the last version (it's stable but not yet fully documented so not yet on the download section ) I'll mail it to you... And I have no time for the moment to do this job

The last version includes :
* Some Windows / SQL Server bug correction. (I finally tested it in this case )
* Reports are available for all table fields

I've got v3.3 :-)