As a consequence, joining Commands to tables or other Commands can significantly slow down report processingĪny data filtering MUST be done in the Where clause of the Command. With inner joins, this frequently means that much more data is brought into memory than will actually be used on the report. Instead, all of the data from the Command along with all of the data from the tables is pulled into memory where Crystal will process the join in memory. When a Command is linked in the Database Expert with other tables or Commands, Crystal is unable to push the joins to the database for processing. What follows are some best practices for working with Commands in Crystal.Ī Command should include ALL of the data required in a report. Crystal formulas cannot be used in a command, so any calculations or filters must use SQL syntax.

So, for example, when connecting to MS SQL Server, the “getDate()” function is used to get the current date but in Oracle it would be “SysDate”. To determine whether a Command can be created for a specific type of connection, open the connection in Crystal the first line under the name of the open connection will be “Add Command”.Ĭommands use the SQL syntax of the database that is being connected to. Commands are available for most, but not all, databases. A Command is a SQL Select statement that the user can write to extract data for a report. In version 9 and newer Crystal has a feature called a “Command”.

Sql prompt where clause warning