If the database has failed and you cannot repair and data will be written to the old database during your re-create surely the failures you have cannot be that bad if you can access all data and objects and still have the thing function?

What exactly are the problems your facing which lead you to say the database cannot be repaired?

So you have a database that is saying it is corrupt, you have no certain way of knowing that you are not making the corruption worse because you are still updating it, and are worried about the downtime while you salvage what data is left.

My advice is to bite the bullet and schedule some downtime where you can copy out of your database everything that is still available.

You should also work out scripts that can check the new database for application integrity. The declared RI you have can deal with physical integrity and warn you of child records with missing parents, etc. However declarative RI cannot warn you if a parent has no children when your application expects that it should have.

Original author: SQL Server FineBuild1-click install and best practice configuration of SQL Server 2014, 2012, 2008 R2, 2008 and 2005.30 January 2015: now over 32,000 downloads.Disclaimer: All information provided is a personal opinion that may not match reality.Concept: "Pizza Apartheid" - the discrimination that separates those who earn enough in one day to buy a pizza if they want one, from those who can not.