It could change because the Query Optimizer changed the execution plan and is applying the CAST within the JOIN before the WHERE clause.

You can create user databases on an SSRS SQL server instance if you want and if the server has the resources for it.

Something like this would work:

With units AS

(

Select Distinct

unit

FROM

dbo.Full_Referrals_Dataset_live

)

SELECT

count(FR.[Unit]) as Actual,

U.unit,

FR.[1st_of_month],

FR.[last_of_month]

FROM

units as U LEFT JOIN

dbo.Full_Referrals_Dataset_live as FR

WHERE

FR.RfR1 = '18 month project'

GROUP BY

U.unit,

FR.[1st_of_month],

FR.[last_of_month];

According to BOL:

2.After adding an article to a publication, you must create a new snapshot for the publication (and all partitions if it is a merge publication with parameterized filters)....

Grant Fritchey (10/7/2013)

---

Jack Corbett (10/7/2013)

---

GilaMonster (10/7/2013)

---

Jack Corbett (10/7/2013)

---

I actually had a recruiter contact me about a contract in NYC with a title of Data Architect that...

GilaMonster (10/7/2013)

---

That's...

Grant Fritchey (10/7/2013)

---

Jack Corbett (10/7/2013)

---

In some...

In some parts of the country that probably...

sam bryant (10/3/2013)

---

I started up a trace yesterday to capture some of the statements. If I take one of those statements which was causing 1.4 million reads, with the...

I'm planning on being there. Of course I have had years...

http://technet.microsoft.com/en-us/library/ms159272(v=SQL.105).aspx

sam bryant (10/3/2013)

---

That was my initial thought, but then when I saw that the query plans were the same before, during, and after the issue, I figured that couldn't be...

Glenn's script is pretty good and I also like Brent Ozar Unlimited's sp_BlitzIndex.

Could be a bad parameter sniffing issue where the cached plan was really only the best plan for the initial parameters passed in.

Yes. Your biggest issue will be security.