Viewing 15 posts - 4,261 through 4,275 (of 5,103 total)
>>I beg to differ, this an insert trigger, the timestamp in the inserted table will be the same as the row inserted in the actual table<<
January 28, 2005 at 9:14 am
if you are using the SQL Server built-in timestamp datatype that join will never work because every time a row is created or affected in any way it will change....
January 28, 2005 at 8:11 am
and adding to rudy_komacsar be aware that your procedure cache will contain numerous execution plans one per database + procedure name combination.
There may be a way to create a partitioned view...
January 28, 2005 at 8:05 am
1st off, there are cardinality issues, if 2 or more addresses get updated in a batch, you only want to update the parent record *once*. Hence the Exists () in...
January 27, 2005 at 9:13 am
here you go!
update UPR1
set Update_Ind=1
from
UPR00100 UPR1
join
inserted new on new.EmployID = UPR1.EmployID and new.ADRSCODE = UPR1.ADRSCODE
join
deleted old on old.EmployID = UPR1.EmployID and old.ADRSCODE =...
January 26, 2005 at 3:19 pm
To answer the second trigger I need:
How 101 relates to 102
One record on 101 to many on 102 ?
or
One record on 102 to many on 101?
and through what keys?
can...
January 26, 2005 at 2:29 pm
Some rules for you:
1. At the begining of the trigger check for @@rowcount
2. Use the if UPDATE(col) on separated columns. Don't mix them up
3. in the where clause compare old...
January 26, 2005 at 1:08 pm
The indexes if used correctly will reduce the amount of work necessary to perform drastically. So just make sure that the ones set up are being used and keep fragmentation...
January 26, 2005 at 11:28 am
You could use EM right click on the server select properties and on the memory tab limit the maximum amount. Or use sp_configure to change max server memory.
this is...
January 26, 2005 at 9:10 am
1. Is 3 million IO transactions per day a lot?
It depends on the Harware I am assuming you are not including reads. Because...
January 25, 2005 at 4:07 pm
This is an expected feature on sqlserver. it won't release the memory that it adquires. If you need to restrict the memory you could set up the max server memory...
January 25, 2005 at 3:47 pm
Because of several conditions may affect the performance on such large table you can try also a modified version of PW solution
Select HeaderID
From Header As h
Where HeaderID In (
Select...
January 25, 2005 at 3:40 pm
The error you are getting just means that a key on the table from where you are trying to delete "customer" has already been used in a row on the...
January 25, 2005 at 2:21 pm
January 25, 2005 at 2:02 pm
Viewing 15 posts - 4,261 through 4,275 (of 5,103 total)