integration services would be the best bet

although in theory you could use windows scheduler and .sql script

might be the status field in mssubscriptions on

distribution database

yes since the error is returned (D) is the correct answer

update table

 set field ='N/A'

where isnull(field,' ')=' '

more than likely  a rights issue

you could turn on the profiler on the remote sql server

looking in the security audit for failed logins

and/or look at the rights on the local...

restore database attain

from disk ='

with standby='d:\undo.ldf'

you have to have the undo for it to be read only

declare @n as int

declare @sql_cmd as varchar(4000)

set @n=3

set @sql_cmd='SELECT TOP '+cast(@n as varchar(10))+' notrans, NOTARJETA, NOCLIENTE

FROM TBMOVIMIENTOS

WHERE NOCLIENTE=10 AND NOEMPLE='+char(39)+'0000000124'+char(39)+'

ORDER BY nocliente, noemple, NOTRANS desc'

exec (@sql_cmd)

should work for 2000

that works for 2005

you must be using 2000

i want my points too

user='bob'

xp_sendmail isnt supported in 64bit

it would be an easier education if it were random servers than just the one

as you can see i have that on it,

this is a management issue, in that management thinks that the server is setup wrong

So...

i have drop and recreated the indexes from production

i have dbcc dbreindexed

there are some documents on

sql not using the index if it isnt an effiecent

index  The simple question...

bad

StmtText StmtId NodeId Parent PhysicalOp LogicalOp Argument DefinedValues EstimateRows EstimateIO EstimateCPU AvgRowSize TotalSubtreeCost OutputList Warnings Type Parallel EstimateExecutions

SET STATISTICS PROFILE ON 25 1 0   1         SETSTATON 0 

(1 row(s) affected)

StmtText StmtId NodeId Parent PhysicalOp LogicalOp Argument DefinedValues EstimateRows EstimateIO EstimateCPU AvgRowSize TotalSubtreeCost OutputList Warnings Type Parallel EstimateExecutions

select order_origination,count(1) from orders --with (index(dt_rcvd))

where dt_rcvd between '2004-10-01' and '2004-10-31'

group by order_origination 26 1 0   1  8.0996399    1.7118025   SELECT 0 

  |--Compute Scalar(DEFINE[Expr1002]=Convert([Expr1005]))) 26 2 1 Compute...

actually all three are currently backups of production

so yes they are identical