my guess is an entry in the param.txt file

microsoft released an update of SQLIOStress called sqliosim: http://support.microsoft.com/kb/231619

clustered indexes are more suited to range-seek (like date ranges). (benefit of having a sequential IO feed because the data is ordered sequential). If you only fetch 1 item at...

You could try this with the BULK INSERT command depending on complexity.

You can perform a transaction log backup. It automatically truncates the inactive portion of the transaction log.

I would start with reducing the batch size.

It was needed at work to reduce it from 500 to 100 because our subscriber was slower in IO

Found the kb:

http://support.microsoft.com/kb/811030

It could be timing out. You can change batchsize & timeout in the replication agent profiles.

Use

execute spAddOpptest @OppName=...

Otherwise it tries to fill the first parameter @OppID int out with your text

It is better to explictly mention the parameternames in case the order of parameters...

I'm interested also if that would be possible.

Only the datecreated is mentioned in the sysobjects table.

*pro.factor isn't in the select, why do you calculate it?

*Is

'CveProyecto Prorateo' = pro.proyecto

testing if pro.proyecto is equal to the literal 'CveProyecto Prorateo'?

*

LEFT JOIN (SELECT factor = gp.factor / (SELECT...

After the installation of Oracle Client software, reboot the server. Otherwise sql server doesn't seem to recognize until reboot.

Hello,

I'm not familiar with ado (and its locking) but you could check the following:

*locks: sp_who2

If the function only has to enter a new record, perhaps you may consider a stored...

You can manipulate the batchsize and querytimeout to reduce the errors.

At work I changed the standard batchsize to 100 and now the replication (on a LAN) won't time out any...

Interesting solution.

Is data_sf quite selective? If so an index on data_sf wouldn't probably hurt to avoid a tablescan for the records to update.

1)Is there an index on data_sf?

2)if it doesn't have to run as a transaction, try splitting it up in batches

(test the following first)

DECLARE @DATEOLD datetime

DECLARE @DATENEW datetime

set @DATEOLD=...

set @DATENEW=...

SET ROWCOUNT...