Optimizing a cursor query in MS SQL 2005

USE [project_management]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE PROCEDURE [projects].[spGetProjectCosts_cursor]
	-- parameter for project id
	@pId int
AS
BEGIN
	-- SET NOCOUNT ON added to prevent extra result sets from
	-- interfering with SELECT statements.
	SET NOCOUNT ON;
 
	-- Declare the variables to store the values returned by FETCH.
	DECLARE @aId int, @aNo int
 
	-- create a cursor to find cost for distinct accounts of the project
	DECLARE account_cursor CURSOR LOCAL FAST_FORWARD READ_ONLY FOR
	SELECT DISTINCT t1.account_id, t2.account_number 
	FROM projects.costs t1
	INNER JOIN finance.accounts t2 ON t1.account_id = t2.id 
	WHERE project_id = @pId
	ORDER BY t2.account_number ASC
 
	OPEN account_cursor
 
	-- Perform the first fetch and store the values in variables.
	-- Note: The variables are in the same order as the columns in the SELECT statement.
	FETCH NEXT FROM account_cursor
	INTO @aId, @aNo
 
	-- Check @@FETCH_STATUS to see if there are any more rows to fetch.
	WHILE @@FETCH_STATUS = 0
	BEGIN
 
		-- Get the costs for this specific account
		-- I have limited the number of columns to one for EE
		SELECT cost_name
		FROM projects.costs
		WHERE account_id = @aId AND project_id = @pId
 
		-- This is executed as long as the previous fetch succeeds.
		FETCH NEXT FROM account_cursor
		INTO @aId, @aNo
	END
 
CLOSE account_cursor
DEALLOCATE account_cursor
 
END