>a.) We have schema (Catalog ) based triggers, how to transport it to different client?
You can't yet. For that we would need a repository representation like the other artifacts. This has been in our backlog for sometime and will hopefully come with SPS 11.
> Is there anyother way to transport tables between different HANA systems except import and export?
If these are replicated tables then you should use SLT. However if these are your own custom tables (created via HDBDD) then you can transport them via DU like most any other development object.
>Also how to track the changes made in table by anyone like we have in ABAP in TR's
Repository created tables (HDBDD) have change/version management.
>Regarding content objects ( package objects ), I have just learned from video, to import export to client, but what needs to be done if it has to
be moved to production and we dont have acces to do the same?
Repository objects (created within packages) should be transported via Delivery Units
>And same question as above, how to track the changes of any object like version management we have in ABAP?
Everything created via the Repository has version management automatically.