This may be a simple Blackberry Enterprise SQL schema question, but we are trying to keep an archive of all handheld changes. There is a SQL table view which is great for tracking cell numbers, BB model numbers, associated users, BB IMEI's, etc..

We already pull active information from this SQL table view (called vHandheldSummaryInfo). Using this SQL table view, it appears that the "ID" column updates/increments everytime a handheld or user change is made. Does anyone know if this is true and if it's the ideal column to key off for archiving?

Here's the sql we are using:

----
INSERT INTO MyHandheldSumArchive
(Id, UserConfigId, ServerTime, ModelName, PlatformVer,
AppsVer, PhoneNumber, IMEI, HomeNetwork, VendorID,
PasswordEnabled, HandheldConfigStatus,
HandheldConfigCheckTime, DCID, FlashSize,
ITPolicyName, ITPolicyTime, PIN, DeviceType,
DisplayName, ServerConfigId, HandheldConfigId,
DeviceCapabilities)
SELECT Id, UserConfigId, ServerTime, ModelName, PlatformVer,
AppsVer, PhoneNumber, IMEI, HomeNetwork, VendorID,
PasswordEnabled, HandheldConfigStatus,
HandheldConfigCheckTime, DCID, FlashSize,
ITPolicyName, ITPolicyTime, PIN, DeviceType,
DisplayName, ServerConfigId, HandheldConfigId,
DeviceCapabilities
FROM vHandheldSummaryInfo
WHERE vHandheldSummaryInfo.id not in
(select distinct MyHandheldSumArchive.id from MyHandheldSumArchive)
----

Any tips or suggestions?