you might have to post your script, but i'm guessing that you have not filtered out stored procs or you have a "dodgy" join in your script.....

looks like we're not the only ones to come up agains this

http://www.geekswithblogs.net/sabotsshell/archive/2005/08/20/50706.aspx

hmm - i've just tried it as well and got the same problem - looks like it's been removed from 2005 since the beta.

documented in 3 of the books i...

should do - but you may find that logging out the user that's getting these errors from all devices should also fix it.

i'm sorry - but some of the recent questions have been a little "open to interpretation" !!!!!

what may work for one situation won't work for another - i can't possibly...

it's a log in failure or connection failure - usually occurs for us when someone changes their password but is still logged into sql server - when they try and...

floating point precision (if they are floats) also the numeric specifications between products are different

you want the insert with merge command (2005)

merge into mytable

using mytemptable

on mytemptable.id=mytable.id

when matched then

update myfield=mytemptable.newfield

when not matched then...

you could also pass in the correct parameters for the index to de rebuilt (not the clustered one obviously) rather than reindexing the whole table

???

can you run the following and send the results back

select @@servername

select serverproperty('machinename')

maybe the machine has been renamed since sql was installed? if so then the 2 vlaues will be...

you'll need to begin trans and commit trans around the statements.

if you're worried about the locking use read uncommited in your select statements

declare @server nvarchar(200)

declare @strsql nvarchar(2000)

declare curs1 cursor for select datasource from master..sysservers

open curs1

fetch next from curs1 into @server

while @@fetch_status=0

begin

set @strsql='select * from '+@server+'.master.dbo.sysusers'

--set @strsql=@server+'.master..sp_who2'--proc version

exec @strsql

fetch next from curs1 into...

i've not heard of Tail log backups before - i think you may be referring to Tee-Log backups (or T-log) which stands for transaction log..... so they are the same...

select * from syscomments will show you all source code from procs, views, functions etc

or join it on sysobjects

select o.id,o.name,c.text from syscomments c inner join sysobjects o on o.id...

ssis isn't included in express edition - you need to upgrade to either workgroup, standard or developer edition.