Backup and restore huge partitioned database - SQL Server: Revision history

27 February 2023

• curprev 16:3116:31, 27 February 2023‎ Luca talk contribs‎ 9,335 bytes +17‎ No edit summary
• curprev 16:1316:13, 27 February 2023‎ Luca talk contribs‎ 9,318 bytes −3‎ No edit summary
• curprev 16:0716:07, 27 February 2023‎ Luca talk contribs‎ 9,321 bytes +1,502‎ No edit summary
• curprev 15:1315:13, 27 February 2023‎ Luca talk contribs‎ 7,819 bytes +722‎ No edit summary
• curprev 15:0915:09, 27 February 2023‎ Luca talk contribs‎ 7,097 bytes +1,907‎ No edit summary
• curprev 14:5814:58, 27 February 2023‎ Luca talk contribs‎ 5,190 bytes +519‎ No edit summary
• curprev 14:5714:57, 27 February 2023‎ Luca talk contribs‎ 4,671 bytes +2,513‎ No edit summary
• curprev 14:2114:21, 27 February 2023‎ Luca talk contribs‎ 2,158 bytes +857‎ No edit summary

• curprev 14:2014:20, 27 February 2023‎ Luca talk contribs‎ 1,301 bytes +1,301‎ Created page with "Category:SQL Server This example fits the case when you have a big database in SQL Server where: * one ore more table are partitioned * one or more filegroup are in readonly, for example filegroups with old data Suggestion: when you have a big database with historical data, it is a good idea to design it similar to this example. In this case you can backup and restore filegroups separately. If you are doing full backups of this kind of database you are wasting time..."