Check out BOL "Using the inserted and deleted tables" for more info.  To summarise, the 'inserted' table is a temporary table that contains a copy of the record (or records)...

You need to use a join to get the best performance.  Indexing on the id fields would also help a lot.

select * from table2 t2

left join table1 t1 on...

Use CONVERT in your SELECT statement to format the results that are returned by the SELECT statement - this will not affect the underlying data:

SELECT CONVERT(blah blah) as NiceDate, ....

will display...

This is difficult to achieve outside of EM - see the following link for more info. if the EM solution is not what you want.

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=126116&p=1

Regards

As you will see if you run this piece of code, your method should work.

declare @temp varchar(10), @service varchar(10), @office varchar(10)

set @service = 'P'

set @office = 'L'

set @temp = @service...

To prove your suspicions, you could try changing the offending select statements by adding WITH (NOLOCK)?  I do not know the answer to your @@isolation question.

Regards

Phil

Chuck, this is certainly possible.  The outline of what you need to do is

select data1, data2, etc

from tablelist

where (change varchar field to date) > targetdate

This does not require you to...

Hmmm - my assumption is surely valid?  Assuming Doctor Who's absence, how can 'dateinput' be a future date?

How about this WHERE clause:

where ContractDate >= cast(floor(cast(getdate() as float)) as datetime)

Phil

I've never used this solution - though I see no reason for any drawbacks - except, perhaps, for the ugly message that could be sent back to client apps -...

Check out this link for more info on this:

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=9&messageid=157147#bm157159

Or you could use

where isnumeric(column1) = 0

Cheers

Phil

Depends on your table - eg does it have a key field that gets bigger and bigger with each new record? Eg if the data look something like this:

ID,...

The multiple [null] occurences are treated as duplicates: the index is therefore not unique and cannot be created as such. As far as I know, there is no simple...

Several ways to do this. One is to create a new calculated field in your Products table:

NumericID = (convert(int,right([productid],6)))

and then it's just a straightforward query to find the next...