Timeline for The smallest backup possible ... with SQL Server
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 28, 2011 at 20:31 | comment | added | SQLChicken | Gotcha. Then as others have said already, the 3rd party vendors like Redgate and Quest have very good backup compression tools to help you meet their needs. Another potential solution is SQL Azure. Right now the database size limit is 50GB but they've lifted the charges for any data being loaded so it might be a cost effective solution. | |
| Jun 28, 2011 at 16:05 | comment | added | jcolebrand♦ | The replication/log shipping was what I had in mind, but that was like two weeks ago, so I doubt it is as important now. Also, I just re-read and saw the part about the Citrix, and I could've told you then (as now) that they don't do that. They just do local development using a DVCS infrastructure and just want the data for testing/playing with/confirmation. Also perhaps for the data dumps. | |
| Jun 28, 2011 at 12:54 | comment | added | SQLChicken | Haha there's lots to consider here. Which point exactly would you like me to expound on? | |
| Jun 7, 2011 at 14:22 | comment | added | jcolebrand♦ | Can you expound on this anymore? I know that this is for the StackExchange team proper, so I'm sure they would love a more indepth walkthrough ;) | |
| Jun 6, 2011 at 2:50 | history | answered | SQLChicken | CC BY-SA 3.0 |