Note that there are some explanatory texts on larger screens.

plurals
  1. POHow can I backup a logical subset of the data in a SQL database?
    primarykey
    data
    text
    <p>We have customers who, for unassailable reasons, cannot use SQL Server's built-in backup features because it backs up the entire database. These customers need to breakup and backup the database into subsets of who owns the data so the appropriate parties can backup their own data according to their own rules. My question is two-fold:</p> <ol> <li>How would I do something like this? </li> <li>Have you ever been asked to partition your backups like this? If not, have you ever been asked to do something that appears to fly in the face of the industry standard? People in our company suggest we/I should simply "roll our own" backup process that backs-up just the required subsets of data. This means, of course, that we/I should simply "roll our own" restore process. When I argue that this is the definition of reinventing the wheel and part of why we chose SQL Server in the first place, I get the sense that they think I am being a tech snob and/or lazy. </li> </ol> <p>I suspect their opinions are based on experience with another product that was Access-based and stored each logical unit in a separate database that could simply be copied.</p> <p><strong>Update:</strong> I finally got around to implementing this by backing up the "complete" database using SMO, restoring the backup, and deleting records from the backup that are not part of the subset. I am quite disappointed to find this resulted in the transaction log growing to upwards of 5GB within a 5 minute period. It seems like creating an empty database and inserting will be easier, but how can I replicate the schema without having a static script that needs to be updated as the database is updated?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload