I think what you are asking is if you can take a backup of just data that has changed recently?

The answer is sort-of. You can take a differential backup...

Lots of things go into coming up with the execution plan for a query in SQL Server. Take a look at the execution plans on each server. It...

I don't think you have captured your requirements all that well in your posting.

From what you have here, my first though would be to use a GUID - then it...

Yes, the scripting that Management Studio generates does. Basically, it just does a table lock on the table you are moving so all other processes will be blocked during...

A SQL Destination will certainly not work with a synonym to a linked server. The SQL Destination needs to be a local SQL Server because of the way it...

You may want to reconsider using FullText for this. A fuzzy lookup in SSIS would probably be more appropriate. It is designed to find "close" matches based on...

IMAGE data is not stored in the data pages of the table, so moving the clustered index (which is the actual table data) does not move your IMAGE data.

If memory...

So you need to change the design AND upgrade your server...

Is this a one-time update, something you intend to do regularly in batch, or something you need to really happen...

If you can, clear your procedure cache. In the procedure, add an OPTIMIZE FOR and specify the variable values you are using when running through Management Studio. The...

That is what I meant by don't multi-task your server. You "could" mirror and then use a database snapshot of your mirror so you can see the data on...

That would probably do it. As another temporary stop-gap option, you could do the check you are doing now with NOLOCK, but when you find a record that you...

I would typically recommend you do not try to multi-task a server and use it for both a DR solution and a reporting solution. They tend to conflict with...

The optimizer may decide to do an index scan if it feels it is going to need a high percentage of the records. This may simply be the case,...

Without looking at the execution plans, I would have to guess that you get very different plans depending on the parameters you pass in. Since stored procedures cache execution...

NOLOCK is a pretty scary thing to use, and you have misused it here. The problem you are having is probably the order being modified is moving from one...