Post reply

Make a backup of SQL Server tables............

  • September 25, 2009 at 7:09 am

    #214856

    I am using SQL Server 2005 and have a question about backing up only a table in the database. and this backup file will be saved on different server and not on the same server where the database is.

  • September 25, 2009 at 7:22 am

    #1058441

    any ideas friends?

  • September 25, 2009 at 7:33 am

    #1058447

    You cannot backup specific objects within a database with SQL Server native tools. You will have to get a third party tool to do this.

  • September 25, 2009 at 7:34 am

    #1058448

    as you know SQL backs up whole databases, so your options are:

    -- a not "real" SQl backup: send the DDL and the data to a text file via BCP, so it can be restored at a different server/time

    -- a real backup: the whole database, so you can restore that table on demand.

    -- copy the table to a different, empty/clean database, and use SQL to backup that db after you copied the table.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • September 25, 2009 at 7:35 am

    #1058449

    Hi,

    I dont beleive there is a way to backup only a table directly within management studio however you have three options;

    1. Backup the whole db to a disk on another server

    2. Backup the table into another SQL instance on a different machine

    3. Use a third party tool to do a table backup, i've heard that some can do it, but i've never used one. Best to google it and see what you find.

    Hope this helps.

    Check out my blog http://www.sqlservercentral.com/articles/Best+Practices/61537/

  • September 25, 2009 at 7:36 am

    #1058450

    Lowell (9/25/2009)

    as you know SQL backs up whole databases, so your options are:

    -- a not "real" SQl backup: send the DDL and the data to a text file via BCP, so it can be restored at a different server/time

    -- a real backup: the whole database, so you can restore that table on demand.

    -- copy the table to a different, empty/clean database, and use SQL to backup that db after you copied the table.

    Lowell beat me to it. 😛

    Check out my blog http://www.sqlservercentral.com/articles/Best+Practices/61537/

  • September 25, 2009 at 7:43 am

    #1058455

    Thankyou all for the suggestions. that's what i was thinking.

  • September 25, 2009 at 7:44 am

    #1058456

    You may want to see some other options from the previous discussion:

    http://www.sqlservercentral.com/Forums/Topic736321-146-1.aspx?Highlight=backup+table

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply