Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a SQL Server database which has grown to more than 15GB in the past 5 years. Now my problem is disk space and the time it takes to run daily backups. What I want to know is how can I archive old records and reduce the size of the database without losing data?
Thanks in advance.
15GB isn’t very big and it should be possible to back it up quickly, even without doing anything special. Since disk space is much cheaper than almost any other technical resource – especially developer or DBA time – you need to ask if it’s really worth designing an archiving solution, or do you just buy more disks.
More fundamentally, what does “archive” mean to you anyway? If you move the data somewhere else, it will still be taking up space and you will have to buy and maintain that space. Is it acceptable to put it on tape or DVD and forget about it, or will you be asked for it from time to time? If so, how often and what delay is acceptable when a user requests it? Are there any legal regulations that you need to follow? Should the data still be visible in your applications but just stored on a different disk? If so, does splitting the data even make sense?