so you could get this :

create proc spc_xxx

as

begin

set nocount on

-- first table is CUSTOMER table that have 2 field (id_cust,id_support)

-- second table is SUPPORT table that have 3 field (id_support,...

is this what you are looking for ?

update Customer

set id_support = S.id_support

from Customer C

inner join  (

 Select id_cust, count(*) as counter

 from rc_sortir_intag

 group by id_cust) CC

on C.id_cust = CC.id_cust

inner join Support...

May I emphasize BP id_columns should not be used but for PK/FK perposes, so a count(*) for id_columns should only determine the number of usage, but nothing else ?!

with int datatype you don't have decimals

you could do

select convert(decimal(11,3),yourIntCol) / 100 as youDecCol 

(adjust...

There has been a bug in sql7 where this osql using sa was a workaround.

now I'm out of ammo

May seem a bit strange, but what happens if you make a sqlagent-job and have it execute the sp/dbcc using OSQL with sa-login ?

e.g.

osql -Usa -Pdontleaveitblank -S yourserver -d master -Q...

Using EM you can't view all jobs, unless you are sa

Maybe this proc can help out using QA :

Use master

go

if exists (select * from dbo.sysobjects...

differential backups are not incremental, they each contain all differences since the last full backup.

If you want to use incremental backups, activate full (or bulk logged) recovery model and use...

Using this sqlagent job, it works fine over here. This job is scheduled on all our servers one a week.

As you can see I encountered a problem using the...

Check out : http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=93754

done

May I add this has been a guideline for quite some time now :

The curse and blessings of dynamic SQL

Keep in mind NOT to have your website run with sa-privilages !

but you'll need security-admin privileges

Keep in mind, one should prefer "least authorities" above "all privileges"

That's how it works for me

 All my sql7 and sql2k servers have these parameters.

I did forget to mention -T3605 makes sqlserver write this...

if you want deadlock-explanation (involved spids and statements) add these parameters to your sqlserver startup parameters :

-T1204

and

-T3605