I don't really understand how what you're proposing applies to my situation.
The tables get regenerated twice daily with new data, save a small handful of reference tables which rarely change and have already been ruled out.
There is no "front end" really since the process is completely...
the database can't be slimmed down, nor can the tables be changed, it supports a 3rd party application that I have no control over in terms of how it manages the data.
the reason it's so massive is that it's for a scheduling program that manages worker time and tool usage down to the minute for...
Here is my problem.
I've been tasked with migrating a system currently built on Access to SQL Server due to the application hitting Access' size limitations.
upon testing the application on the development machine I found that we are getting different results than the production machine...