It is dependent on the license of PTReportGen you have purchased. For detailed information, see Licenses.

The SQL Execute window offers the ability to execute Transact-SQL queries from within your Great Plains SQL version system without needing additional SQL Administration Utilities loaded. The result set can be displayed as text or as a Listview. However, one of the best features is that you can use Dexterity Technical names when writing your query and they will automatically be converted into the correct physical name for the field or table prior to execution.

The TCL time or clock commands are useful for timing statements. More information is available in the documentation.

The highest-level function to do this is PyRun_SimpleString() which takes a single string argument to be executed in the context of the module __main__ and returns 0 for success and -1 when an exception occurred (including SyntaxError). If you want more control, use PyRun_String(); see the source for PyRun_SimpleString() in Python/pythonrun.c.

Hi there - I am new to Oracle (used to Ingres).I am having trouble creating a database.I keep getting the following oracle errors.ORA-01501ORA-01519ORA-00604ORA-30012Can you tell me what I am doing incorrectly?Many thankseibbed

One can call DDL statements like CREATE, DROP, TRUNCATE, etc. from PL/SQL by using the "EXECUTE IMMEDIATE" statement (native SQL). Examples: begin EXECUTE IMMEDIATE 'CREATE TABLE X(A DATE)'; end; begin execute Immediate 'TRUNCATE TABLE emp'; end; DECLARE var VARCHAR2(100); BEGIN var := 'CREATE TABLE temp1(col1 NUMBER(2))'; EXECUTE IMMEDIATE var; END; Users running Oracle versions below Oracle 8i can look at the DBMS_SQL package (see FAQ about Dynamic SQL).

Yes, run the "Queries with Table Hints", "Queries with Query Hints", and "Queries with Join Hints" to find this information. Please, keep in mind that the filtering option: "Show Top (in %): N" will filter the top queries with most executions and then it will check them for Hints usage; this lowers quite a bit the impact on the server when running this report. reports.

Starting from Oracle8i one can use the "EXECUTE IMMEDIATE" statement to execute dynamic SQL and PL/SQL statements (statements created at run-time). Look at these examples. Note that the statements within quotes are NOT semicolon terminated: EXECUTE IMMEDIATE 'CREATE TABLE x (a NUMBER)'; -- Using bind variables... sql_stmt := 'INSERT INTO dept VALUES (:1, :2, :3)'; EXECUTE IMMEDIATE sql_stmt USING dept_id, dept_name, location; -- Returning a cursor..

Yes, run the "Query Optimizer" report. It will provide you with different statistics including the use of hints (i.e. table, join, plan, etc.)

There is no direct way to execute operating system commands from PL/SQL. PL/SQL doesn't have a "HOST" command, like in SQL*Plus, that allows users to call OS commands. Nevertheless, the following workarounds can be used: Write an external program (using one of the precompiler languages, OCI or Perl with Oracle access modules) to act as a listener on a database pipe (SYS.DBMS_PIPE). Your PL/SQL program then put requests to run commands in the pipe, the listener picks it up and run the requests.

SQL Editor provides you with an ability to execute several queries simultaneously. Each query is executed in a separate thread, so all MaxDB Maestro features remain available and there is no need to wait for your complex query to be completed.

The standard query methods (Database#execute, Database#execute2, Database#query, and Statement#execute) will only execute the first statement in the string that is given to them. Thus, if you have a string with multiple SQL statements, each separated by a string, you can’t use those methods to execute them all at once.

No, the spectrum of statements within the report refers to all participants. At least one of the possible options applies to everyone. You need to mark statements that touch you. We are all unique in the combination of elements that make up our personality. At the same time, we all pass through the same stages of development which are biologically given and experience the same conflicts between these drives and the environment.

Direct SQL mode of the Database Retrieval component allows freely-formatted SQL SELECT statements of any degree of complexity to be added to the procedures. The SQLCommand system function can be used to run SQL statements that add, update and delete rows in the database tables.

P6Spy is a transparent JDBC proxy-driver specialized to log the statements performed against the actual driver you normally would use. Using p6spy would allow to log the SQL statements issued by DbUnit. Move spy.properties into a directory listed in your classpath. Unlike JAR files, you do not directly reference your property file in the classpath (e.g.: if you have the file c:\r\proj\conf\spy.properties make sure you put c:\r\proj\conf in the classpath). Modify the realdriver line in the spy.

OJB ships with out of the box support for P6Spy. P6Spy is a JDBC proxy which delegates all JDBC calls to the real JDBC driver and traces all calls to a log file. P6Spy is contained in the p6spy.jar, which you'll find in the lib folder of your OJB distribution. Add this to the classpath of your app (if you're using the ojb-blank project, then simply copy the jar into the lib folder of the project and if you're using Eclipse then also add it to the project build path).

ColdFusion will automatically escape an apostrophe if it's in a variable value that you're inserting into a database. It escapes it by doubling it up from ' to ''. For exmple, if Var1 and Var2 contain apostrophies, you don't need to worry about escaping the following code.

All content in between <CFQUERY> and </CFQUERY> is sent to the database via the database driver as is. Unlike CFML, SQL is not typeless, and so SQL statements must be complete and valid as per SQL syntax specifications. All strings (or variables being used as string values) must be enclosed within singe quotes. Similarly, all numeric values must not be within quotes, and all dates and times must be formatted as valid date and time values.

There are a couple of sql statements that cannot be executed inside a transaction. User and db space creation are examples of such statements. These are special statements that seldom you will need to synchronize. DbUpdater executes first these statements and then starts a transaction for all the other sql statements. As a consequence, rolling back the transaction will leave these entities changed.