Tabel Level Backup-Sql Server 2008 R2

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2008 Forums

SQL Server Administration (2008)

Tabel Level Backup-Sql Server 2008 R2

Author

Topic

mast80864
Starting Member

4 Posts

Posted - 2012-07-30 : 07:11:13

Hi ,

I have a table to store various information after hitting payment gateway from my application which stores more than 100000 records per month(all are text/string).

Now my table is having 3000000+ records. I would like to take back up for that specific table year wise(ex: 1st March 2011 to 31st March 2012) so that i can delete whole records after back up task is over.

Having these many records many issues from Business Logic layer level. Please suggest me best way to back up and delete specific records(Yearly ) from table.

Thanks and Regards
Mastan

nigelrivett
Master Smack Fu Yak Hacker

3385 Posts

Posted - 2012-07-30 : 07:21:14

Unless these are very wide it shoouldn't be an issue. How much data are you talking about. It's probably just the queries that need to be changed and maybe the indexing.

If you want to archive then you might consider a partitioned table - partitioning by month - then it's just a matter of swapping partitions in and out - put them on filegroups for backups and deletes.

==========================================
Cursors are useful if you don't know sql.
SSIS can be used in a similar way.
Beer is not cold and it isn't fizzy.

mast80864
Starting Member

4 Posts

Posted - 2012-07-30 : 09:46:40

Hi,
Thanks for quick response and tabel details are as follows.

Index Space: 0.008 MB

Row count : 2570716

Dataspace 325.617 MB

Does it creates performance problem if a table has data like above..

Thanks
Mastan

nigelrivett
Master Smack Fu Yak Hacker

3385 Posts

Posted - 2012-07-30 : 09:49:07

Pretty tiny. You shoouldn't be seeing much in the way of performance issues here - I would check your queries.
It doesn't look like you have any indexes which could be the issue.

==========================================
Cursors are useful if you don't know sql.
SSIS can be used in a similar way.
Beer is not cold and it isn't fizzy.

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources