The point with my example (and David's) was just to show how to shuffle using NEWID()

Just create your 'deck' table with the cards you need, and then you could probably...

If you can modify your action, you don't need a trigger for this.

For insert, just insert getdate() into the column, for an update, set LastUpdateDate = getdate()

It is possible to...

In what way does it 'fail' then..? Errormessages? Nothing happens? Other things than the expected happens? Permission problems? Object not found problems?

.. there are quite a few reasons as to what...

EXISTS is a boolean expression - IN is a list.

EXISTS returns only true or false - no data from the expression in an EXISTS clause is returned. EXISTS also stops...

An easy way to generate a 'random' sequence is to order by NEWID()

Here's showing the principle:

create table #deck ( card int not null )

declare @i int

set @i =...

It sounds like the entire remote table is fetched across the wire before the search is done..?

I don't do much linked servers, so I'm not sure what causes this, I...

Why implement it as a function?

What happens if you just do

SELECT @DOB = DOB FROM <serverName>.Demographics.dbo.Demographics WHERE Patient_ID = @PID

..?

/Kenneth

That's what I did. Both methods produce identical query plans - and both methods also produce the same argument. Even though you write WHERE col1 BETWEEN 'x' AND...

Some agreements and some disagreements

Not equal operators by their nature never uses any indices, they always force a table scan - that's why...

AFAIK, not out of the box.

There are however quite a few hits if you google for "SQL Server and Visual Sourcesafe integration".

/Kenneth

Some thoughts....

You really shouldn't attempt to send mail from within the trigger - it'll only annoy your boss even more, sooner rather than later. You never want to do external...

Well, this may be a bit tricky - not to produce the format, but the ddmmyyyy is not a valid date, so you can't use any convert styles. Also, you...

I liked Joe Celkos 'SQL for smarties' - not platform specific, it's more a 'generic SQL' book - but it gives you some food for thought.

Also, another favorite is Ken...

Well, if the trigger doesn't do anything than call an insert or update procedure, then you're stuck. With that design you're forced to cursor through each insert or update - which...

Triggers (as you have found) fire once for every update, not once for every row.

To deal with this, the trigger should be written in a way that handles more rows...