good advice.....but it would be even better to put that SQL code into a Stored Procedure....better performance, better datatype checking, better security, better split of DB responsibility between front-end +...

Sounds like while you are changing the connection string to point to the new server, you are not (re)establishing the connection to the new server afterwards....

I'd agree...please post a sample...

Cheap and cheerful....put a series of "typcial" scripts (select + updates, etc) together that can be randomly called by some utility....possibly either off the schedule or via multiple client sessions.

For...

"Put the 'read only' copy on a development server."....that is what I implied...I was expecting an element of mind-reading

Setup read-only copy of production for developers to run their queries against.

"disable all jobs for next 1 hour. So that they won't be refired in that 1 hour window."....would it not be simpler to just disable the SQLAgent for 1 hour???...at what...

I don't ring Anhauser-Busch when I see their ad's either.  Advertisers shouldn't expect a 100% response rate.  Not being upfront about price ranges also...

Your issue now makes sense given that this is the 'replication' forum.....I must at the forum title more to get the context of the question.  You may benefit by posting...

Is this a table named "conflict" or a table with which there is some data load which generates "conflicts"....your problem description is too vague.

You will have to provide DDL and...

Ability "to execute" is far more important than any "paper that says you passed an exam".....as is the ability to fit in and work with the new team.

Don't treat the SAN as 1 big lump of disk space....segmenting the SAN into different areas (for data, logs, temp files, etc) would be advantageous in terms of performance.

Can you give us an example with sample data???...involving parent and child data (+ table DDL?)

The cheap way would be to schedule a 'master job' to run every minute....and for it to call the 'slave job' 6 times....seperate by a (near) 10second delay....trouble there is...

1. Undo the RAID setting...RAID brings a data storage overhead.  I know it's useful, but it does have a capacity cost.

2. Investigate file compression as a possible solution to increasing...

Quite possibly you have a bottleneck elsewhere in your application that is preventing the CPU breaking 7%.  Optimisation is an ongoing exercise in (re)moving bottlenecks...you solve one problem, you move onto the...