Try looking up "Parameter sniffing"

You might have a shot at getting it to behave better with this simple change:

create procedure [dbo].[CalculateActivityTotal] (

@periodstartdate datetime = '2007-01-01',

@periodenddate datetime = '2007-01-08',

@hsgradyearstart int...

Try:

select twd.*

from

TransWorkDetail twd

INNER JOIN TransLineItem TLI on twd.SalesLineItemId =tli.SalesLineItemId

INNER JOIN TransHeader th on th.TransHeaderID...

Jeff Moden (1/15/2008)

---

Adam Haines (1/10/2008)

---

Adam... just so you know, that function doesn't actually work... it returns a zero for positive numbers AND returns a "domain error" if @NBR happens to...

Ray - take a little closer look at Andras' signature....:D

I'd say it's a fair bet that he has...

Steve Pitt (1/15/2008)

---

I don't want to hire the best candidate if it's obvious that they'll only be with me until they'll find something better - I don't have time to...

Michael Valentine Jones (1/15/2008)

---

Joseph Hicks (1/15/2008)

---

You should be aware that the MAC address can be changed dynamically, so a restriction based on MAC address is not foolproof.

The old DECnet protocol...

Nope - still wouldn't use periods. The fact that it would only rarely end up in T-SQL doesn't much change what others have already mentioned in my mind.

Of course...

Are you continually testing this thing using Query analyzer or SSMS? If you are - you might simply be getting that because the temp table isn't being cleaned up...

I call that "changing the bag on the coffee infusion"....:w00t:

The only downside I've heard is something about a "security flaw" which when described seemed a bit far-fetched to me. Because the file doesn't reinitialize the data - it...

A few thoughts:

- If you can't fill the position for long periods of time, or you seem to only get marginally qualified people, perhaps it's time to either change...

Now keeping in mind that dynamic SQL can be very dangerous when you use it around GUI system (SQL injection ,etc....) You could try something like this

Declare @myTable sysname

declare @columnnames...

In short - at any time between the BEGIN TRAN and the COMMIT.

So -

BEGIN TRAN

(do whatever you need to do)

(test that it did what you want)

COMMIT TRAN

or

ROLLBACK

Keep in...

Try rewriting it as a dervied table instead of a CSQ and see if you get more results. If you don't - skip the highlight criteria, turn that oin...

Jeff...