Why do you need to combine the two statements into one? However you manage to accomplish that, you will inflate the size of the resultset being passed over the network unnecessarily.
I suggest combining the two statements into a stored procedure instead:
CREATE PROCEDURE GetAllData (@NumberOfRecipients int output) AS BEGIN
SELECT C.*, M.members_Email
FROM tbl_Campaigns C
JOIN tbl_Members M ON C.campaign_MemberId = M.members_Id
WHERE C.campaign_MemberId = @userID
ORDER BY C.campaign_Key DESC
SELECT @NumberOfRecipients = COUNT(*)
FROM tbl_CampaignRecipients
WHERE recip_CampaignId = C.campaign_Key
AND (recipient_Status = 3 or recipient_Status = 4)
END
In your client-side code, you would call it like this:
- Create a command object for the
GetAllData
stored procedure.
- Attach a parameter object for the
@NumberOfRecipients
parameter.
- Execute the command.
- Consume the default resultset.
- Read the
@NumberOfRecipients
parameter value (this must be done after consuming the resultset).
C# example:
using(SqlCommand command = new SqlCommand("GetAllData", connection)) {
command.CommandType = CommandType.StoredProcedure;
SqlParameter recipientsParam = new SqlParameter("@NumberOfRecipients", SqlDbType.Int) { Direction = ParameterDirection.Output };
command.Parameters.Add(recipientsParam);
using(SqlDataReader reader = command.ExecuteReader()) {
// consume the resultset
}
// read the parameter
int recipients = (int) recipientsParam.Value;
}
You can also re-use the stored procedure in server-side T-SQL code, e.g.:
declare @NumberOfRecipients int
insert into #Results execute GetAllData @NumberOfRecipients output