vikingDBA (8/25/2011)
I don't know how crazy this is going to sound, but here goes:Create one database, with one set of tables. In each table, put two additional columns, one for user and one for DatabaseID (I can't remember what the different databases stood for, so I'll use DatabaseID as the column name).
:w00t: it really sounds crazy 😀
The fact that"it will work" doesn't mean that's the best solution.
Let me ask this, taking into consideration that you are running "n" databases on the same set of tables, obviously on the same instance.
Acme Corp, which data is in Database "n=3" wants the database recovered as it was yesterday at 3:15PM EST... how in the world are you going to recover it without trashing the other "n-1" databases running in your "shared" system? 😎
Nice try 😀
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.