I have to say that i think i agree with your developers.

this seems to be very open to interpretation, but i think that if you have table values that are...

which hotfixes?

i think 2162 was withdrawn for a few months and then replaced because it was faulty.

exactly right.

always always enforce referential integrity through the db. if your app fails because of DRI then its not a good app

mostly developers don't use foreign keys and constraints because...

yes you can

but it will usually end in someone crying

the sql server will also protect it from executing endlessley and will stop it at the nesting level set...

i just tested it as i've not seen these scripts before and have no problems at all - no x required.

are you using the revised version posted most recently?

other than...

select * from table1 where field1 like N'% %'

you could also do something like

select * from mytable where field1ltrim(rtrim(field1)

but this would be very bad against large tables

also

select * from...

create proc myproc @unit nvarchar(10)=NULL,@invdate datetime=NULL,@invno nvarchar(10)=NULL

as

declare @strsql nvarchar(1000)

set @strsql='select * from mytable where 1=1 '

if @unit is not null

begin

set @strsql=@strsql+' and unit='''+@unit+''''

end

if @invno is not null

begin

...

i do agree with the other guys here - set based is always best but sometimes you don't have a choice

the only way i can see you doing this is...

you might be able to find a lot of this information (and more) by downloading sqldiagnostic manager from idera.com

there's a 28 day free trial and it's about £600 ($1000) per...

use mydatabase

go

dbcc updateusage(mydatabase)

go

sp_msforeachtable @command1= 'sp_spaceused ''?'''

go

with the restore it could be one of a few things. more than likely it's the I/O speed when trying to create the files (how big is your database?)

or perhaps...

not sure this is exactly what you're looking for but how about

select amountid,count(*) from amount group by amountid where amountid>0

this should then have the same values in the resultset

select amountid,count(*)...

redgate and imceda both provide backup compression tools to do this

imceda's sql litespeed is particularly good, but they've been bought out by quest, so the prices have gone up

2 things you can do

1)stop sql agent -it uses msdb so you won't be able to restore

2) if that fails right click ont eh database and choose properties and set...

the log % used is 0.18981564% so i'm guessing a backup or switch to simple must have occurred at some point