I am facing a dilemma. I wonder if SC allows the used of SP (Stored Procedures) for MSSQL.
I have a number of complicated statements in a Stored Procedures with a lot of variables which is required to filter out the statement. The statement consists of many “INNER JOIN” “UNION”, and “WHERE” to filter out the final result.
I cannot declare the variable in SC to filter out the result because some of the statement consists of variables that must be declared in advance so that the SELECTED results can be populated into the #temp table and “JOIN” with the earlier results to be used with other statements.
SC provides direct linking to the tables/views only.
Is there a turn around for SC to handle complicated SP and still can make use of the simplicity of SC? The ideal solution is to be able to use the entire SP in SC and all the variables declared in MSSQL SP will automatically be switched over to SC’s variables…
Please help!
Thanks