I have many stored procedures with SQL statments that have
many joins and 'where' clauses which make it very hard to
figure out while certain data are being duplicated in the report. It's very time consuming trying to figure out
whether it's a data problem or a logic problem in the
statement. I am thinking that it will be a lot easier to
track down the problem if i break out the SQL into many
stored procedures and I debating whether to write the
between result sets into a cursor or a temp table.
Is this a better solution than leaving the SQL in one SP??
Is a cursor better than a table? include a view instead?
Thanks.
many joins and 'where' clauses which make it very hard to
figure out while certain data are being duplicated in the report. It's very time consuming trying to figure out
whether it's a data problem or a logic problem in the
statement. I am thinking that it will be a lot easier to
track down the problem if i break out the SQL into many
stored procedures and I debating whether to write the
between result sets into a cursor or a temp table.
Is this a better solution than leaving the SQL in one SP??
Is a cursor better than a table? include a view instead?
Thanks.