Hi Dheeraj,
Few things here... first as you are probably already aware, we no longer support SDM 12.5 at this time as it is no longer in service. We would highly recommend that you upgrade to the latest version of the product (14.1) as soon as possible so that you can open support cases and we can assist you with these types of issues. As for the RAM usage in SQL, it can be caused by any number of things - there are many factors that can lead to excessive RAM usage on a database server. For that I would work to recommend that you talk to your SQL DBA who should be able to run some diagnostics to see what queries are causing SQL to use that much RAM etc. As for the size of your database, that is fairly large, and for that I would recommend setting up archive and purge rules to run during off hours to purge out older data. Archive and purge does not compress anything, it actually removes old, non-needed data. You can read about the details of using the archive and purge functionality on the documentation site (which is currently working intermittently today as some problems are addressed - so I cant provide you with an exact link to that page at the moment). Lastly, regarding the bulk_load of assets in the ca_owned_resource table, we do not support manual loading of assets or CIs to the MDB. We only support importing assets/CIs by using the GRLoader (general resource loader) utility. That is also documented in the documentation on the doc-ops site as well. Once the site is working normally, I can provide you with those links.
Hope this helps a bit,
Jon I.