Implement the "IGNORE" rules so that database objects can be completed filtered out of source control
Introduce something similar to the "IGNORE" rules found in your Schema compare for Oracles solution to the SQL Server Source Control product.
The problem that exists for those of us with third party databases that have 10's of thousands of objects is that they are not workable using this product because it ONLY applies the filter AFTER it has already tried to extract and manage the ENTIRE database. The "IGNORE" option would allow us capabilities similar to filter but they would be applied UP FRONT and BEFORE the system ever tried to gather and manage every single object in the database. This is important because we actually only desire to ever manage the objects we are not ignoring or filter out. Without this capability the software crashes and runs for hours upon hours working hard on all of these objects that we DO NOT even want to ever manage.
This has been discussed by Redgate support, developers and product managers and I am hoping your votes will help to get this worked on ASAP as it is mandatory for success in our environment.
This is a critical component to add Database change / version automation with app source code. Im betting this is desired by other customers as well.
Mike Richards commented
Great idea. Would be very helpful enhancement.