the thing is i dont want it to hit the db everytime someone wants to see a diff table in the report.

I'd rather have it filter the results after...

THIS WILL RETURN THE COUNT OF RECS FROM THE tTracking_tblReportsUsage FOR A GIVEN REPORT_ID AND IF THAT REPORT_ID DOESNT EXIST IN THE tTracking_tblReportsUsage TABLE THEN IT WILL RETURN 0....

SELECT COUNT(*)

FROM

(

SELECT r.stockcode, p.type FROM

(

...

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

The order in which you place these things and whether or not you place the criteria in the ON or WHERE cluase (at least for INNER JOINS) does not matter....

I'm interested to find out if the order of the constraints in the where matters as well. I would have to thik it does.

Inner Joins:

If i'm writting production level stored procs that must be optimized then i would put everything that exist in the ON statement in the WHERE as well when using...

oh and by the way. Personally i realize there is always a solution by using dynamic sql. However, you should stay away from it at all costs unless u absolutely...

In the above situation the product changes were coming as xml messages because the changes were actually happening off site and then adjusted on our side. it was really cool...

I wrote the stored procs for this at hsn for product updates and it was similar except the proc call was based on an xml message. just like u said...

by the way the only way around this was to use the 'master.dbo.xp_cmdshell. The idea was i wanted to loop through all our active sql instances and do a...

i found where it is being defined.

it appears the subscriber_id is coming from the srvid in the master.dbo.sysservers table

i personally think this will perform the best. Simply because it is or-less. Or's hurt. Sure it may be a little hard to wrap your mind around which will hurt...

GROUP BY ALL will be removed in a future version of Microsoft SQL Server. Avoid using GROUP BY ALL in new development work, and plan to modify applications that currently...

Trying to think back where this wouldf have burned me in the past.

declare @colA CHAR(3)

declare @colb CHAR(10)

set @colA = null

set @colb = ...

thanks...