☰

Updated Using Stored Procedures In Izenda 6 (markdown)

CaseyStokes committed 2016-03-18 12:27:24 -0400 commit d35915bfc3b57423f502910cfa5379cc8542f880

				FAQ/Questions/Using-Stored-Procedures-In-Izenda-6.md
			
          @@ -224,7 +224,7 @@ string currentReportName = HttpContext.Current.Request.QueryString["rn"];

           Since Izenda primarily uses metadata to obtain information about schemas, views, and other database objects, the same goes with stored procedures. Therefore, there are some expectations to be followed for these procedures that are to be used with Izenda.

          -Izenda Sends NULL values to all parameters and expects to receive column headers with no data in return. This allows Izenda to create a temp table for the StoredProcedure to be reported on and joined like a view. 

          +Izenda sends NULL values for all parameters and expects to receive column headers with no data in return. This allows Izenda to create a temp table for the StoredProcedure to be reported on and joined like a view. 

           * INSERT EXEC - You cannot nest INSERT INTO ... EXEC statements in stored procedures used with Izenda. This is a limitation of SQL server.

           * Return columns - The stored procedure MUST return the same columns in all cases. It is because the metadata expected when running the stored procedure must comply with the specifications given to it.

...	...	@@ -224,7 +224,7 @@ string currentReportName = HttpContext.Current.Request.QueryString["rn"];
224	224
225	225	Since Izenda primarily uses metadata to obtain information about schemas, views, and other database objects, the same goes with stored procedures. Therefore, there are some expectations to be followed for these procedures that are to be used with Izenda.
226	226
227		-Izenda Sends NULL values to all parameters and expects to receive column headers with no data in return. This allows Izenda to create a temp table for the StoredProcedure to be reported on and joined like a view.
	227	+Izenda sends NULL values for all parameters and expects to receive column headers with no data in return. This allows Izenda to create a temp table for the StoredProcedure to be reported on and joined like a view.
228	228
229	229	* INSERT EXEC - You cannot nest INSERT INTO ... EXEC statements in stored procedures used with Izenda. This is a limitation of SQL server.
230	230	* Return columns - The stored procedure MUST return the same columns in all cases. It is because the metadata expected when running the stored procedure must comply with the specifications given to it.