Changes in 36ab7f8: Updated Using Stored Procedures In Izenda 6 (markdown)

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

                 }    

               }

           }

          -```

          \ No newline at end of file

          +```

          +

          +##Best Practices with Izenda

          +

          +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.

          +

          +* 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.

          +* Temp tables - You can build temp tables with the stored procedure and return that as long as the rules above are followed. Just ensure that the returned value is not null. This allows Izenda to obtain metadata from the empty result set of the stored procedure.

          +* Multiple values as one parameter - It is possible to pass multiple values as a single parameter. For instance, you can construct a comma separated list of values and pass that resulting string to the SP. It would then be possible to split the string into its respective parts within your SP.

          \ No newline at end of file

...	...	@@ -218,4 +218,13 @@ string currentReportName = HttpContext.Current.Request.QueryString["rn"];
218	218	}
219	219	}
220	220	}
221		-```
...	...	\ No newline at end of file
	0	+```
	1	+
	2	+##Best Practices with Izenda
	3	+
	4	+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.
	5	+
	6	+* INSERT EXEC - You cannot nest INSERT INTO ... EXEC statements in stored procedures used with Izenda. This is a limitation of SQL server.
	7	+* 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.
	8	+* Temp tables - You can build temp tables with the stored procedure and return that as long as the rules above are followed. Just ensure that the returned value is not null. This allows Izenda to obtain metadata from the empty result set of the stored procedure.
	9	+* Multiple values as one parameter - It is possible to pass multiple values as a single parameter. For instance, you can construct a comma separated list of values and pass that resulting string to the SP. It would then be possible to split the string into its respective parts within your SP.
...	...	\ No newline at end of file