working with large databases

Question

0.00/5 (No votes)

See more:

Hi,

We use sql server 2008 database and c# windows application.We use for 10 years same database so increased in size of database.I think that we have received the necessary measures in Software To speed up database operations.We do not have too much experience in the sql server management.For example, We think create the archive database.

1.We backup current database,
2.delete all data from the current database used to create a blank database.

But to achieve this with the old and new data will need to open two connection.

Is there an application in SQL Server management for database archive ?

How do Companies working with large databases find a solution to this problem by SQL Server?

Thanks in advices.

Posted 27-Sep-11 0:38am

eraydeniz

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Pradeep Shukla · Answer 1 · 2011-09-27T04:34:00

You need to define the archival criteria as to which data or how old data you want to archive. Now either you can move this data to a separate database or to a separate file group. In first scenario you would have to connect to two Dbs and in the latter you don't have to do that. Once this purge is done run all your indexes and use dbcc shrinkfile to compact all the files. These links can provide you some more useful information:
http://vyaskn.tripod.com/sql_archive_data.htm[^]
http://www.mssqltips.com/sqlservertip/1121/archiving-data-in-sql-server/[^]