Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 7,2000
»
Strategies
»
Strategic Advice for Unique Requirement
Strategic Advice for Unique Requirement
Rate Topic
Display Mode
Topic Options
Author
Message
sqlislife
sqlislife
Posted Wednesday, October 14, 2009 11:16 AM
SSC Journeyman
Group: General Forum Members
Last Login: Thursday, March 07, 2013 11:19 AM
Points: 99,
Visits: 165
Hi Experts,
I have a very unique requirement and I need some advice on the best strategy to tackle it. I have 5 tables with a combined data of about 358 million rows (22GB). out of those 5 tables, 1 of them (2GB) is actively queried. I need to consolidate all 5 tables into one table that would be queried from time to time. Here is what I think should be done i.e. my ideas
-Consolidate the other 4 (non queried table) first into one table
-Move the 5th active table data to this new table
Are there better ways to achieve this? What about locking on the actively queried table when moving data? Would I really need to partition (date range) the 22GB data or indexes would do just fine for querying?
Any suggestions from you experts would be greatly appreciated. Thanks
Post #802957
PaulB-TheOneAndOnly
PaulB-TheOneAndOnly
Posted Tuesday, January 19, 2010 8:34 AM
Hall of Fame
Group: General Forum Members
Last Login: Today @ 12:22 PM
Points: 3,017,
Visits: 4,471
May I ask what is the rationale behind such a consolidation project?
The most active/queried to-be-consolidated table represents less than 10% of total data volume... why would somebody add to this table ten times more data that is not normally needed?
From the performance point-of-view this looks to me like creating a proble in a place where there are no problems; in short, if it's not broken - don't try to fix it
_____________________________________
Pablo (Paul) Berzukov
Author of
Understanding Database Administration
available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Post #849797
SQLRNNR
SQLRNNR
Posted Tuesday, January 19, 2010 9:33 AM
SSCoach
Group: General Forum Members
Last Login: Today @ 3:33 PM
Points: 18,858,
Visits: 12,443
I agree that this seems like an effort in the wrong direction. Consolidating these tables, based on limited information, does not seem to be a good idea.
Jason
AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server 2008
SQL RNNR
Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #849860
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.