aa45c89d3f3da389d43dc89d94494fb898c9b230
FAQ/Questions/Using-Stored-Procedures-In-Izenda-6.md
| ... | ... | @@ -6,12 +6,12 @@ |
| 6 | 6 | |
| 7 | 7 | Since version 6.0, Izenda Reports can expose existing SPs (Stored Procedures) in MSSQL databases as DataSources for designed reports. This tutorial explains how you can create the appropriate SP in MSSQL 2005, and include it as a DataSource in a report. The Northwind sample database will be used in the examples. The main considerations are: |
| 8 | 8 | |
| 9 | -* Creating or using an existing stored procedure in MSSQL 2005 |
|
| 9 | +* Creating or using an existing stored procedure in MSSQL |
|
| 10 | 10 | * Making SPs visible in Izenda Reports |
| 11 | 11 | * IMPORTANT- Filtering the Equals select drop-down |
| 12 | 12 | * Building the report |
| 13 | 13 | |
| 14 | -##Creating SPs in MSSQL 2005 to use in Izenda Reports |
|
| 14 | +##Creating SPs in MSSQL to use in Izenda Reports |
|
| 15 | 15 | |
| 16 | 16 | When SPs are detected in your MSSQL database, their names will appear in the list of available DataSources in the Report Designer. Currently, Izenda AdHoc supports only input parameters, while parameters of other types are ignored. Input parameters play the role of the columns that are used in the WHERE clause of the SELECT statement. |
| 17 | 17 | To be suitable for AdHoc, SPs must return a standard SELECT statement. This will be treated as the result of a standard SELECT statement being performed on a table. The column names returned from the SP will be available as fields in your DataSource. |