Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server 2005: Transactional replication between hard drives on same server


SQL Server 2005: Transactional replication between hard drives on same server

Author
Message
schwzac
schwzac
Forum Newbie
Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)

Group: General Forum Members
Points: 2 Visits: 44
I'm relatively new to SQL server development in a non-collegiate scenario, so i will try to be as concise as possible.

Our production server handles a lot of queries every day from many sources(sales dept.,our website, amazon, reporting, etc...). When the server begins to noticeably slow we have found that the server resources aren't maxing out. The data choke point seems to be the hard drive read/write speed.

(This is how it was explained to me, and I have been given the task of researching this possible solution.)

My question is: can you use transactional replication to replicate a database on another hard drive within the same server? We want to do this to offload all our reporting to the separate hard drive so the main hard drive is only handling orders without replacing hardware or building a second server. Sort of like an internal data warehouse.

Any help is much appreciated.
Orlando Colamatteo
Orlando Colamatteo
SSCrazy Eights
SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)

Group: General Forum Members
Points: 8243 Visits: 14368
There really is not enough info to say for sure what would be best for you, but one misconception I picked up is "choke point is read/write speed of disk" and I think it might be worth keying on to start a dialogue. Data is not read directly from disk unless the data required to satisfy a query is not present in memory, i.e. all data that is returned to satisfy a query is first loaded from disk to the buffer pool unless it is already in memory. The goal for SQL Server is to keep as much of the most-used data in memory as possible because it will result in better performance. If the problem traces back to the fact that data needs to be loaded from disk on a regular basis then tuning your queries and indexes so less data needs to be read to satisfy your queries, or the hardware solution of adding memory, is more likely to give you a higher return on investment than doing what you're talking about with adding another disk and replication.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
schwzac
schwzac
Forum Newbie
Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)

Group: General Forum Members
Points: 2 Visits: 44
I had a chat with my superior regarding your enlightening reply, and with that in mind he has decided to "...research an alternative solution."

Thank you for your helpful response, and thank you for being patient with my novice questions.
Orlando Colamatteo
Orlando Colamatteo
SSCrazy Eights
SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)

Group: General Forum Members
Points: 8243 Visits: 14368
Anytime. Thanks for the feedback.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search