July 8, 2008 at 9:09 am
Guys,
We have recently added a new SQL Server 2000 instance, which has identical database structure as a few other servers we had. We have transaction replication set up, and this server was added as a subscriber, getting all its data from the publisher. Now, while its data is identical to all the rest of the subscribers, it is not yet used by our clients (i.e. it is not yet considered a production server). As such, I wanted to take this opportunity to tune it as much as possible (since it is sort of in its downtime).
Could anyone advise what is best to be done at this point in time?
For example, should I rebuild the indexes or do anything else?
Thank you for any input!
July 8, 2008 at 11:46 am
Does your new instance is on a shared server? If so, your test during peak time will affect other applications.
Identical data is not enough to do a test. You should add the same indexes, triggers, ... In short, everything should be the same to simulate your source server.
A question at the end, what do you mean to "tune it"? Index and query tunings should be carried out before building your replication, should not you?
July 8, 2008 at 11:51 am
I'd rebuild all indexes, which will update statistics and ensure things are OK, including removing fragmentation. I might double check the fill factors, checking if I need less or more space on pages.
July 8, 2008 at 3:44 pm
I was not clear enough. Yes, everything is totally identical. And the new server does not share anything with any other servers.
I did rebuild the index, so I guess I'm ok.
Thank you!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply