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.

you're looking for an rss feed such as the one provided at

http://ansuz.sooke.bc.ca/rippy/exchange/

dump transaction has been deprecated in 2005 use backup log (apparently backup log with truncate_only has also been deprecated)-

but if the primary in the mirror has not synchronised with...

then new primary or the old primary ?

when you say - can't dump the log - why not ?

alter database x set restricted_user

should stop anyone who isn't dbo dbcreator or sysadmin getting in the database

in sql2005 you have to add a job to the maintenance plan for "delete maintenance plan files" - this can be performed before or after the backup itself (i recommend...