is there any script in SQL Server to archive database from older to new

Question

0.00/5 (No votes)

See more:

i need a script to move older data from Test database to archive database. Suppose i have a db who's size is 10GB and it is getting full frequently,so i need a script, whenevr i run this script, i want older data(for ex: data beyond 1 month) should move to another db who's size is 100gb and append this data there

Posted 7-Jan-16 18:49pm

JasonClark03

Add a Solution

2 solutions

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)

Wendelius · Accepted Answer · 2016-01-07T19:22:00

As far as I know there's no general script for archiving since the rules for archival process vary depending on the business rules of the database.

The amounts of data (10 GB and 100 GB) sound very small in overall so have to ask, why archiving? If the reason is performance, I'd suggest going through indexing of the database instead splitting the data into two separate databases (which introduces extra complexity). Depending on the edition you use I'd even consider partitioning if indexing doesn't yield sufficient results: Partitioned Tables and Indexes[^]

Abhinav S · Accepted Answer · 2016-01-07T19:53:00

Solution 2

You can look at the transaction log file.
You can back it up and create a new one (shrink existing one).

Try - Manage the Size of the Transaction Log File[^]

Posted 7-Jan-16 19:53pm

Abhinav S

Updated 7-Jan-16 19:54pm

v2