Could it be that the saturday backup job is still running because of the ongoing stored procedure?

Are you taking 2 full backups on saturday (one regular, one stored procedure after...

Hello

1. Are there any db parameters for configuring # of processes for the db, simultaneous sessions per user, idle_time for a session etc.

->So far I know this is a...

You can compare the execution plans with query analyzer. (Show (estimated) query plan.

I guess with literals the optimizer immediately figures out is it one date (index seek), with variables an...

declare @datelast datetime

declare @dateprevious datetime

set @dateprevious='20070101'

set @datelast='20070102'

/*find items that are in

inventorylast but not in inventoryprevious

*/

select inventorylast.SKU

,inventorylast.qty int

,inventorylast.invdate

from inventory inventorylast

where not exists

(select 1 from inventory inventoryprevious

where inventorylast.sku=inventoryprevious.sku

and ...

Probably needs some refining since you use dateadd

declare @datestart datetime /*start of period*/

declare @dateend datetime /*end of period*/

set @datestart='19990906'

set @dateend = '19990917'

select roomnumber,rate

from room /*check al rooms if in not...

Always mention the column names when inserting. In case someone decises the names have to be alfabetically sorted.

insert into Sep_92 (Regno,Payment) values (19,'2005/12/05')

You can rebuild indexes with DBCC INDEXDEFRAG OR DBCC DBREINDEX

Shrinking parts of the database can be done with DBCC SHRINKFILE

It is fine to have primary keys with "no meaning". Mark the other unique fields with unique indexes/constraints and eventually a foreign key so later on you still will able...

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...