Help us help you next time by providing consumable sample data as I have done.
WITH SampleData (EmailID, Email, [Status]) AS(
SELECT 6207,'abbdie@nofavtt.org',2
UNION ALL SELECT 6207,'abbdie@nofavtt.org',5
UNION ALL SELECT 6207,'abbdie@nofavtt.org',2
UNION ALL SELECT 5011,'abhayy.bisarya@ncickc.com',2
UNION ALL SELECT 5011,'abhayy.bisarya@ncickc.com',2
UNION ALL SELECT 5011,'abhayy.bisarya@ncickc.com',5
UNION ALL SELECT 5011,'abhayy.bisarya@ncickc.com',5
UNION ALL SELECT 1236,'abigaill@abigailhueller.com',2
UNION ALL SELECT 1236,'abigaill@abigailhueller.com',5
UNION ALL SELECT 2283,'accent@mcleodusa.net',3
UNION ALL SELECT 5522,'achung@kebus.com',2
UNION ALL SELECT 5522,'achung@kebus.com',2
)
SELECT EmailID, Email
,[% Open] = 100.*COUNT(CASE WHEN [Status]=1 THEN 1 END)/COUNT(*)
,[% Click] = 100.*COUNT(CASE WHEN [Status]=2 THEN 1 END)/COUNT(*)
,[% Unsub] = 100.*COUNT(CASE WHEN [Status]=3 THEN 1 END)/COUNT(*)
,[% Conversion] = 100.*COUNT(CASE WHEN [Status]=5 THEN 1 END)/COUNT(*)
FROM SampleData a
GROUP BY EmailID, Email;
Merry Christmas!
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St