The DMX_Repository Table size has gotten pretty large in my DNN DB. 2534424KB
I am holding my data on Amazon S3 now and I am wondering if that Repository should still be large even after moving all the files to S3?

well I ran some of the size scripts and clean up in the admin and the size went down to 48KB

scratch that. it is still 2534424. i was looking at the wrong thing. any ideas?

Hi Brandon,

You can run a query to remove content from that table. It is important to verify whether the file actually made it across to S3. Here is the SQL that should do this:

DELETE FROM DMX_Repository
FROM DMX_Repository r
WHERE NOT EXISTS
(SELECT e.EntryId FROM DMX_Entries e
WHERE e.[Entry] = CAST(r.BlobId AS NVARCHAR)
AND e.PortalId=r.PortalId
AND e.StorageProviderID = 2)

Note: probably it's a good idea to backup the db just in case.
Note 2: you can also check to see if there are any files left in SQL according to DMX by running
SELECT e.EntryId FROM DMX_Entries e WHERE e.StorageProviderID = 2
The StorageProviderID for S3 is 3.

Peter

that worked! thank you.