Hans,

I do Agree with you that it sounds like totally unreasonable design, I just tried to show that it is posible to do it. I don't know what is the...

>> I really hope you gave an example of such a trigger, and that you did not really have the result in mind, or else you'll be in for a...

This is a classic problem what method to use the flag or the LockedTable

For scalability purposes I would recommend you use the Locks...

I think it can be done, Just Haven't tried. But I would recommend to disable the NESTED Trigger option (which it is by default). Therefore the rows inserted in the...

JT

if looping is performing an expensive select, cursors are a great alternative. locking can exists while you walkthrough the cursor but if it allows you to take one pass only...

sys* tables in tempdb are row-locked in Sql2K

what about NORMAL sys* tables

select * into #Tbl1 from MYTABLE  <-- Effectively lock the schema on...

create table #Tbl1

( ItemNo char(6), ItemInfo char(60) )

Insert into #Tbl1 (ItemNo, ItemInfo) Values('3000','FL            01       0       Ý   00000000     00V        ')

Insert into #Tbl1 (ItemNo, ItemInfo) Values('3001','FL            01       0       Ý   00000000     00V       ...

What are you talking about?

I don't have a clue on what the model is supposed to be because is not mine!!!

The root of the problem that the original poster has...

The model was just to show graphically the cycle to the poster it was not meant to be a full blown ER diagram. if you look at is is all...

It is NOT true. "Select Into" is a non logged operation therefore extremely fast. When you have a table already created you have no choice but to use insert into...

No problem

I have seen this more than once and I was forced to look for the MSBPA to show some of my...

Best Pricatices dictate that EVERY FIELD in queries where there are more than one table or view should be qualified with table name like: tblname.fldName.

Now, Do that on you query...

     DEV                                                   Employees

 ------------                                            ------------

|   DevID    |  ----------------------------------------|   EmpID    |

|------------  /                                         ------------

|   EmpID    |/                                        -|   RoomID   |

|------------                                         /  ------------

I don't see any place where the code checks for drive mappings. And you know why? Drive mappings belong to USER PROFILES which SERVICES (like SQL SERVER ) have no knowledge...