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

Why am I being blocked by spid -1? I am not able to kill it and have to restart SQL Server to get around it. Why does the new 'TOP' command in SQL 7 not work? I get a syntax error. Also ALTER TABLE and other SQL 7 only commands.

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.

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

Tcl is a shortcut for Tool Command Language. This language has a huge pool of successfull users around the world. We decided to integrate Tcl in our software, because the language is very easy to learn. We extended the Tcl language with some new powerfull multimedia commands that let you animate, navigate and control Javanti presentations.

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

Assuming that you have a pressing need to call Tcl from Perl/Tk then one "official way" to so would be via the ->send() and the ->Receive() methods. It is also worth noting that you can still have access to a complete Tcl script from perl via the perl system, or '' (backtick), or even exec mechanisms. Just be careful with I/O waits and return values if you try one of these approaches. Further suggestions may be found in the various perlipc files at: ftp://ftp.perl.

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.

The answer here is not to put the data in your SQL statements at all, but to use parameters. Every data provider worth using provides a way of specifying parameters in SQL statements, either named (e.g. SELECT NAME FROM PEOPLE WHERE ID=@ID) or positional (e.g. SELECT NAME FROM PEOPLE WHERE ID=?). Some providers only support positional parameters, others only support named parameters, others support both.

Within the PA61 transaction, when creating or editing infotypes, you may hit F9, record text and save that entry.  It creates an icon on the screen you can click on to see the text. That is the only way to see the entry. It doesn't appear if you choose 'overview' for an infotype or if you choose list entry What is the code "Z021 Process Adverse Weather" used for? We are guessing that it is used to recoup pay for an Adverse Weather day if time was not made up by an employee.

Considering that both interpreters/(compiler) for Tcl and Perl were written in C for original use on Unix computers it is not surprising that there are some similarities between the two languages. Nevertheless, there are a large number of differences between the Tcl language and the Perl language. One thing to keep in mind is that to build, install, and use Perl/Tk one does not need to have Tcl/Tk on hand at all. Perl/Tk is completely independent of Tcl/Tk.

Nick Ing-Simmons has written a (rather lengthy) tcl2perl script. It is distributed with the Perl/Tk build kit. Please handle carefully! (translation: do not expect it to translate arbitrary tcl code accurately nor even into the most efficient Perl/Tk equivalent. Do go over the converted script with care - and do not forget -w and use strict;.) Thanks Nick :-)

Tcl 8.2 requires Expect 5.31. Either upgrade to Expect 5.31 or go back to Tcl 8.0. (I recommend upgrading.)