Database Backup

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Administering » Database Backup

13 posts, Page 1 of 2

1 2 »»

Database Backup

Rate Topic

Display Mode

Topic Options

Author

Message

Sachin-558788

Posted Monday, January 17, 2011 4:41 PM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, September 21, 2011 11:19 AM
Points: 8, Visits: 26

Hi,
I have a huge database whose backup file goes around 20 GB, because we store all documents in image format into the table.
Since we need to backup this DB everyday, this requires a lot of space in server.
All i want to do is:
1. Back whole database without that single table every day.
2. Back up that single table separately as separate bak file.. may be every week.. if possible in separate server.

Is there any way we can do this in MN SQL?
Thanks in advance.

Post #1048990

Adiga

Posted Monday, January 17, 2011 9:50 PM

SSCommitted

Group: General Forum Members
Last Login: Thursday, May 16, 2013 3:50 AM
Points: 1,618, Visits: 20,898

Sachin,

SQL Server does not have an option to backup a table as a .bak file. You can make use of SSIS to export the tables.

Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga

Post #1049044

Sachin-558788

Posted Monday, January 17, 2011 10:02 PM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, September 21, 2011 11:19 AM
Points: 8, Visits: 26

Hi Pradeep~,
Thanks for the reply.
My document table is about 10+ GB with Image column in it. I don't know exporting this table in a file works for me.

Also, Do you know if we can backup database with our that 1 table? If we can please do let me know..

Thanks
~Sachin

Post #1049048

Adiga

Posted Monday, January 17, 2011 10:05 PM

SSCommitted

Group: General Forum Members
Last Login: Thursday, May 16, 2013 3:50 AM
Points: 1,618, Visits: 20,898

Native backups to disk does not support excluding objects. SSIS is a good option for you to export the table to another database.

You can create a database to store the single exported table and then take the backup of that table to disk.

Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga

Post #1049050

Sachin-558788

Posted Monday, January 17, 2011 10:34 PM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, September 21, 2011 11:19 AM
Points: 8, Visits: 26

Thank You Pradeep!!
I appreciate your comments...

Sachin

Post #1049056

khushbu

Posted Monday, January 17, 2011 11:19 PM

SSC Veteran

Group: General Forum Members
Last Login: Monday, January 21, 2013 11:50 PM
Points: 267, Visits: 695

It seems like a big database. You can also consider 3rd party tools like LiteSpeed which can help you backup/restore one table.
Ofcourse it is a license tool.

If licensing is problem , SSIS is the best option.

Post #1049072

Keith Langmead

Posted Tuesday, January 18, 2011 12:56 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, May 01, 2013 8:28 AM
Points: 144, Visits: 423

You could split that one large table into a separate filegroup, then use filegroup backups to backup the two filegroups separately, which should do what you're looking for.

Post #1049094

Evil Kraig F

Posted Tuesday, January 18, 2011 1:20 AM

SSCertifiable

Group: General Forum Members
Last Login: Saturday, May 18, 2013 10:09 PM
Points: 5,658, Visits: 6,100

^ This.

Sachin, what Keith said above is your best practice, and should usually be done anyway when dealing with LOB data (VARCHAR(MAX), text, Image, etc.) LOBs behave annoyingly when it comes to their storage, and it's best to try to keep them out of the rest of the data, at least anything that won't store in-row.

Look into filegroup backups, and also into differential backups. The two combined should help your storage issues immensely.

- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions | Forum Netiquette
For index/tuning help, follow these directions. |Tally Tables
Twitter: @AnyWayDBA

Post #1049108

Grant Fritchey

Posted Tuesday, January 18, 2011 7:38 AM

SSChampion

Group: General Forum Members
Last Login: Today @ 3:06 AM
Points: 13,371, Visits: 25,153

Unless I'm reading this wrong, 20gb is very small as databases go. I agree that seperating out the storage to different filegroups would allow you to break up the backup process. You might also consider looking at SQL Server 2008 and the FileStream as a means of moving the LOB out of your database and into a file system. But if you're hitting serious space issues at 20gb, I'd strongly recommend getting some more disk space. I picked up a 2tb external drive for $90. I wouldn't recommend that for a data drive for a system, but it might be a good place for storing backups, especially on what sounds likea commodity system.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software

Post #1049352

steveb.

Posted Tuesday, January 18, 2011 7:45 AM

SSCrazy

Group: General Forum Members
Last Login: Wednesday, May 08, 2013 7:42 AM
Points: 2,802, Visits: 7,103

I have to agree 20gb is not large at all - I would concentrate on getting enough space for a standard backup before worrying about any other options outlined

Post #1049357

« Prev Topic | Next Topic »

13 posts, Page 1 of 2

1 2 »»

Permissions