Summary: I'd like to alter some DB scripts to add clustered indexes so they work better for MSSQL (and work at all for SQL Azure). How should I go about this?

New to contributing to OTRS and to the dev mailing list so please forgive me if I stumble around a bit.

I wanted to set up OTRS on Azure using a SQL Azure database back-end, so I thought I'd play around a bit.

SQL Azure apparently chokes when confronted with tables that don't have any clustered indexes. Womp womp.

As of v3.3.5, the setup script for OTRS apparently creates 33 tables without clustered indexes or primary keys (the list in full is at the end of this post). This leads to inoperability and a ton of errors in the log when attempting to use OTRS with SQL Azure.

I'd like to help out with this and submit a pull request for the MSSQL setup to deal with this (as well as make things a little more snappy for MSSQL users). Was hoping to start this out as a Github issue, but I don't believe Issues are enabled for the otrs/otrs project.

However, I'm as of yet completely unfamiliar with the data structure, so I would be guessing at best here and I don't think that's wise. :) 

Is there a solid reference point for the database architecture available that I could reference to deduce where primary keys or clustered indexes could be used in the affected tables? Or is there some other approach the community would prefer I take to addressing this?

OTRS is a great product, and I'm looking forward to being able to hopefully give something back.

Thanks,

--
Sean

Found by running: