September 9, 2011 at 1:54 am
After you purge the data you can shrink and rebuild the indexes, Be careful as to what size you shrink to or you will have fragmentation.
If you move data from one Database to another you are not going to free up space unless you store the Archive Database on another Server but I would not recommend this.
Your users are probably going to want both the unarchived and archive data for their queries.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
September 9, 2011 at 5:33 am
Ivan Mohapatra (9/9/2011)
will the transfered 6 gb data will be automatically compressed to around 3 to 4 gb after doing archive.
I don't understand. It's 2011. I've just bought a hybrid SSD drive of 256 GB for 100$. That's 0.25$ per GB.
Why are you so darn insistant on those 3-4 GBs?
September 9, 2011 at 7:41 am
If you are going to take 8GB from the Database and archive it to a Database on the same Server then you are not accomplishing anything with respect to space.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
September 9, 2011 at 11:49 am
There's no such thing as an archive database or a regular database. Just like there's no "sales" database or "customer" database. These are arbitrary terms we are giving to the database, but it's a database.
If you transfer 8GB of data into a database, it takes 8GB. You can compress the data if you have enterprise edition, but you could compress the data in the regular database as well.
You don't need as much of a space pad in your archival database, but since you might rebuild an index or two, or even index differently, you might need more or less space available for indexes.
September 9, 2011 at 12:09 pm
Ivan, "Archive" is a simple word with many possible complexities.
it might help if you could explain your goals. What is the current environment ? What do the users need ? What are you trying to accomplish ? What are the business needs ?
Then someone here might be able to guide you to a solution.
August 2, 2015 at 10:31 am
homebrew01 (9/9/2011)
Ivan, "Archive" is a simple word with many possible complexities.it might help if you could explain your goals. What is the current environment ? What do the users need ? What are you trying to accomplish ? What are the business needs ?
Then someone here might be able to guide you to a solution.
ok, thank you very much.
I inherited these databases so I'm very green but thank you.:-)
I will get back to you. Have a great day.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply