Archived data showing in same MSSQL table for production data?

MKF62

I'm having problems... I have enabled archiving on an SDE feature class so it could be used in Collector. Now when I got to MSSQL management studio and open up the table, it's showing all the archived data that was deleted. It was my understanding that data that exists should be in one table and data that did exist but was deleted should be in a separate archive table. What's going on? How do I fix this? Just to give you an idea...

This is the table with collected, existing data. It has 13 records:

 

This is what the same feature class looks like on the backend, in SQL management studio. Note, it returns 277 rows. I had a bunch of people testing the application in the field, so they created a bunch of dummy data and then deleted it via the Collector application. Yet is still shows in the backend table?:

George_Thompson

I would think this is by design. It keeps all the records in the same table for querying in the future. The ArcGIS client only shows the "valid/active" data in the view. You can query previous edits/records based on time/dates.

https://pro.arcgis.com/en/pro-app/help/data/geodatabases/overview/the-archive-process.htm

I will only create a separate table when you disable archiving: https://pro.arcgis.com/en/pro-app/help/data/geodatabases/overview/disabling-archiving.htm

Geodatabase‌