Just a guess.  @@rowcount is returning the rowcount from the current context (in this case, the trigger).

How about using

IF (select count(*) from INSERTED) = 0

instead?

How about

EXEC databasename.dbo.sp_autostats tablename

You might want to try the "-W" option.  From BOL:

-W

This option removes trailing spaces from a column. Use this option along with the -s option when preparing data that...

This doesn't match the syntax from BOL, for example:

 CASE ProductLine

         WHEN 'R' THEN 'Road'

         WHEN 'M' THEN 'Mountain'

         WHEN 'T' THEN 'Touring'

         WHEN 'S' THEN 'Other sale items'

         ELSE 'Not...

Sysindexes contains an approximate row count and is accurate right after statistics are updated.  If you need to know EXACTLY how many rows are in a table count() is the...

I don't knowif this is related, but I've seen this happen if the session that creates the view doesn't have the correct setting for the ansi_nulls and ansi_warnings set before...

I'd try this first:

Select the input parameters

SELECT @DefaultDate, @EmpId,@CusId,@hiDay, @loDay

so you can ensure they're being passed correctly.

Take the single quotes off the 0 in the @loDay definition

Take the # off the...

What error are you getting?

You're missing a single quote at the end of 'MY Job'.

I've always used 2 types of criteria to decide what data goes where.

Logical:  Is this data related to the other data by application or business function?  Is this data logically...

I don't know what classes you've had, but I'd also recommend some foundational knowledge on the relational model.  Chris Date's books are, IMHO, the de facto standard basic text.  While...

From the MSDN site:

That's so cool!  But I'm having trouble finding this documented anywhere and when I run the following:

drop

table #mytable

go

drop

They're not the same because EM uses the rowcounts in sysindexes ( or the Information_Schema equivalent) to give you an APPROXIMATE row count, while count(*) actually counts the rows.  Updating...

Hmmmm. The requirements seem a little vague.  I'll make the assumption that this XML stream, or the XML stream it describes, should be an input argument into a stored procedure.  What...

My understanding is that you'd need 15 CALs (one for everyone who could hit the server).