The CA SDK has been deprecated as of version 6.9 and I'm not sure how well supported it was to begin with. My recollection was that it was mainly intended as a way to pull data OUT of the CA database rather than putting data in. Furthermore, even if you do go down this path, you would still want be VERY careful about what data you inject into the database as 95% of the events recorded into the native Windows Event Log are "noise" and are of little to no value. As Aidar noted, the InTrust product is built to work out-of-the-box with native Windows and other types of events. In its current form, it is very easy to get up and running (very comparable to CA) so you might want to trial it rather than throwing time at developing a way to pollute your CA database.
The CA SDK has been deprecated as of version 6.9 and I'm not sure how well supported it was to begin with. My recollection was that it was mainly intended as a way to pull data OUT of the CA database rather than putting data in. Furthermore, even if you do go down this path, you would still want be VERY careful about what data you inject into the database as 95% of the events recorded into the native Windows Event Log are "noise" and are of little to no value. As Aidar noted, the InTrust product is built to work out-of-the-box with native Windows and other types of events. In its current form, it is very easy to get up and running (very comparable to CA) so you might want to trial it rather than throwing time at developing a way to pollute your CA database.