PL/SQL Toolkit reference manual

Could you please provide me with the URL for accessing the PL/SQL Tookit reference manual?
Thanks.

http://otn.oracle.com/docs/products/ias/doc_library/1022doc_otn/apps.102/a90099/toc.htm
good luck

Similar Messages

SQL toolkit

I've added sqldistsupp.dsn and sqldistsupp.exe in my distribution kit to configure a database's connection automatically.
In order to get connection to SQL Server instead MS Access what changes in the sqldistsupp.dsn I have to do?
Thanks

Hello YG,
I have not been able to find an example for this, but you may want to check out the LabWindows CVI SQL Toolkit Reference Manual. Chapter 2 has more useful info on the database connections that are possible.
Regards,
Shawn S. | NIC
Instrument Driver/IVI PSE
National Instruments

Oracle 7 SQL Reference Manual

I am new with Oracle and require the reference manual to find out more about join conditions. I have some difficulty finding a document from the Oracle web on SQL reference.

Oracle 7 is out of support, thats why it is no longer online available.
But to find out more about join conditions you can search the 8i and 9i documentation on
http://tahiti.oracle.com

Where are the SQL and PSQL reference manuals gone ?

Hello,
I cannot found the SQL and PSQL reference manuals on OTN. In previous version of this web site, there was direct links available, but they seem to have disappeared. As a SQL developer, I have frequently to search in those manuals:
- Oracle8i SQL Reference Release 8.1.5 A67779-01
- Oracle8i SQL Reference Release 2 (8.1.6) A76989-01
- Oracle8i SQL Reference Release 3 (8.1.7) A85397-01
- Oracle9i SQL Reference Release 1 (9.0.1) A90125-01
- Oracle9i SQL Reference Release 2 (9.2) A96540-01
- Oracle8i PL/SQL User's Guide and Reference Release 8.1.5
- Oracle8i PL/SQL User's Guide and Reference Release 8.1.6
- Oracle8i PL/SQL User's Guide and Reference Release 8.1.7
- Oracle9i PL/SQL User's Guide and Reference Release 9.0.1
- Oracle9i PL/SQL User's Guide and Reference Release 9.2
I found in this forum links to Oracle9i SQL Reference
Release 2 (9.2) and PL/SQL User's Guide and Reference
Release 2 (9.2), but I would appreciate to have links in the OTN page. Why did you change this ? I must now use Google to search the informations that I need.
Regards

FYI, all the Oracle manuals are online at http://tahiti.oracle.com. There is also a SQL & PL/SQL statement lookup feature that strikes me as a bit easier than using the manual.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Is SQL Connection Function or API Availble in SQL Toolkit 2.2 (Urgent) ?

Hello,
I have build an application using LabWindows 2010 and SQL Toolkit 2.2. Is there any function or dll or api availble so that i do not want to make connection in control panel ODBC ?.
Regards
Umer
Solved!
Go to Solution.

Hello,
The manual for this toolkit might be a good reference for you: LabWindows/CVI SQL Toolkit Help
There is a function called DBConnect, which allows you to connect to a database programmatically. The Help says:
"Purpose: Opens a to a database system to allow execution of SQL statements. Calling DBConnect is equivalent to calling DBNewConnection and then DBOpenConnection"
There's also a page in the help titled Connecting to a Database, which tells you more information about how to use DBConnect:
"Use DBConnect to connect to a data source. The only parameter is a connection string, which must contain the data source or provider name and any other attributes the database requires. DBConnect returns a handle to the database connection that other functions in the toolkit use. Call DBDisconnect to close the database connection, passing in the database connection handle from DBConnect. The following code is a simplified version of the code found in connect.prj.
int hdbc = 0; /* Handle to database connection. */
int rescode; /*Result code. */
/* Connect to CVI_Samples data source. */
hdbc = DBConnect ("DSN=CVI Samples");
if (hdbc <= 0) goto Error;
/* Disconnect from database. */
resCode = DBDisconnect (hdbc);
if (resCode != DB_SUCCESS) goto Error;"
Hope this helps.
Taylor B.
National Instruments

Why do I get a class conflict between the Prepare SQL.vi and the Get Column Name.vi with the SQL Toolkit compatibility vis from the Database Connectivity Toolkit?

I have done extensive programming with the SQL Toolkit with LabVIEW versions through 6.1. My customer now wants to upgrade to Windows 7, so I am trying to upgrade to LabVIEW 2009 (my latest purchased version) using the Database Connectivity Toolkit, and the SQL Toolkit Compatibility vis. Everything seemed to be going okay with the higher level SQL operations, but I ran into trouble with the Get Column Name.vi.
The pictures below show the problem. The original SQL Toolkit connected the Prepare SQL.vi with the Get Column Name.vi with a cluster of two references, one for connection, and one for sql. The new compatibility vis have a class conflict in the wire because the Prepare SQL.vi contains a cluster with connection, and command references, but the Get Column Name.vi expects a cluster with connection and recordset references.
How do I resolve this conflict?
Thank You.
Dan

I've never worked with the old version of the toolkit, so I don't know how it did things, but looking inside the SQL prep VI, it only generates a command, and the the column name VI wants a recordset. I'm not super familiar with all the internals of ADO, but my understanding is that is standard - you only have the columns after you execute the command and get the recordset back. What you can apparently do here is insert the Execute Prepared SQL VI in the middle and that will return what you need.
I'm not sure why it worked before. Maybe the execute was hidden inside the prep VI or maybe you can get the column names out of the command object before execution. In general, I would recommend considering switching to the newer VIs.
Try to take over the world!

How can I use SQL TOOLKIT concurrently with Database Connectivity ?

I have installed LabVIEW 6.1 with the Database Connectivity Toolkit and the SQL Compatibility Toolkit (e.g. _SQL folder). I am trying to make the transition from the SQL Toolkit VIs to the Database Connectivity toolkits, but for compatability with existing systems I would like to be able to run the two sets of VIs concurrently (but not in the same app).
When I read into 6.1 a connection VI that I wrote with LabVIEW 6.0 and the SQL toolkit the connection reference type gets changed from a number to type connection (see attachments) . Does compatbility mean that my SQL toolkit VIs are converted to a form compatible with the new ADO ?
Can I use the SQL Toolkit VIs or the Database connectivit
y VIs in the same installation of 6.1 ?
Can I have the SQL Toolkit VIs appear on the functions pallette and function as they did when only the SQL toolkit was installed ?
Attachments:
CNNCT.vi ‏20 KB
CNNCT.vi ‏22 KB

In response to your #2 below:
Actually it is possible to have the old SQL Toolkit and new Database
connectivity in the same installation of LabVIEW. I have only tried it on
6i, but don't see why it wouldn't work on 6.1. The trick is not to install
the SQL toolkit compatabitily VI's. The old SQL toolkit uses the Intersolve
dll through ODBC while the new Database connectivity uses ADO so it is
possible to use both methods not only in the same LabVIEW install, but it
the same running application. It has been a while since I originally did
this, so I am posting only to mention that it is possible and not exactly
how to do it. If anyone is interested in more details just respond.
Brian
"Jeff B" wrote in message
news:[email protected]...
> First, direct answers to your direct questions:
>
> 1. Does compatbility mean that my SQL toolkit VIs are converted to a
> form compatible with the new ADO ?
>
> Yes
>
> 2. Can I use the SQL Toolkit VIs or the Database connectivity VIs in
> the same installation of 6.1 ?
>
> No
>
> 3. Can I have the SQL Toolkit VIs appear on the functions pallette
> and function as they did when only the SQL toolkit was installed ?
>
> No
>
>
> Now an elaboration:
>
> Having the old SQL Toolkit and the new Database Connectivity Toolset
> installed on the same version of LabVIEW on the same computer is not
> supported.
>
> Once you install the Database Connectivity Toolset, any VIs written
> with the SQL Toolkit will run, but with the ADO layer, as you
> suspected.
>
> Internally, the only way we can have both the SQL Toolkit and the
> Database Connectivity Toolset installed on the same computer for
> troubleshooting customer issues is to have them installed on different
> versions of LabVIEW. I, for example, have LabVIEW 5.1.2, 6.0.3, and
> 6.1 all installed on my computer, and I have the SQL Toolkit install
> on LabVIEW 5.1.2, and the Database Connectivity Toolset installed on
> LabVIEW 6.0.3. In this configuration I can still run SQL Toolkit VIs
> independent of the Database Connectivity Toolset if I open and run
> them in LabVIEW 5.1.2.

Error in PL/SQL Language Reference .... could be that possible ?

I use Oracle 10g ....... but when I used that function in :-
Oracle® Database
PL/SQL Language Reference
11g Release 1 (11.1)
B28370-02
September 2007
page 252
CREATE OR REPLACE FUNCTION compute_bonus (emp_id NUMBER, bonus NUMBER)
RETURN NUMBER
IS
emp_sal NUMBER;
BEGIN
SELECT salary INTO emp_sal
FROM employees
WHERE employee_id = emp_id;
RETURN emp_sal + bonus;
END compute_bonus;
The following equivalent SELECT statements invoke the PL/SQL subprogram in
Example 8–5 using positional, named, and mixed notation:
SELECT compute_bonus(120, 50) FROM DUAL; -- positional
SELECT compute_bonus(bonus => 50, emp_id => 120) FROM DUAL; -- named
SELECT compute_bonus(120, bonus => 50) FROM DUAL; -- mixed
====================================
and than executed first select statement ..... it pass successfully
but in second and third select ...... I found this errors :-
SQL> SELECT compute_bonus(120, 50) FROM DUAL;
COMPUTE_BONUS(120,50)
8050
SQL> SELECT compute_bonus(bonus => 50, emp_id => 120) FROM DUAL;
SELECT compute_bonus(bonus => 50, emp_id => 120) FROM DUAL
ERROR at line 1:
ORA-00907: missing right parenthesis
SQL> SELECT compute_bonus(120, bonus => 50) FROM DUAL;
SELECT compute_bonus(120, bonus => 50) FROM DUAL
ERROR at line 1:
ORA-00907: missing right parenthesis
is there any relation between that I use oracle 10g and those errors ???
or the code wrote wrong in oracle reference 11g ( I hope not ) ???

yes, you are correct. the "what's new" section of the 11g pl/sql manual states
"Before Release 11.1, a SQL statement that invoked a PL/SQL subprogram had to specify the actual parameters in positional notation. As of Release 11.1, named and mixed notation are also allowed. This improves usability when a SQL statement invokes a PL/SQL subprogram that has many defaulted parameters, and few of the actual parameters must differ from their default values."

Set password for DSN (SQL Toolkit)

Hello everybody,
I'm working on WinNT4.0 with LV5.1.1 and SQL Toolkit v5.0. I've got an ODBC
DSN for an Oracle7 database. I'm asked for a password when I make a connection
to the DSN, which I now enter manually.
After that I can read and write data to the database.
Does anybody know how I can set the password automatically with the SQL Toolkit
to avoid the dialog ?
Otherwise there always has to be a user present when a connection to the
database is made, which would be very unkomfortable.
Is there any solution ?
Many thanks in advance.
Ralf.

Wire a string constant to the SQL Connect VI's Connection Parameters input
and include the appropriate connection parameters. For MS SQL7 the info
looks like this:
UID=username;PWD=password
I don't use Oracle, but I imagine it would be similar. If your unsure, create
a file DSN using the ODBC administrator in NT and mimic the parameters it
creates.
"Ralf Erdmann" wrote:
>>Hello everybody,>I'm working on WinNT4.0 with LV5.1.1 and SQL Toolkit v5.0.
I've got an ODBC>DSN for an Oracle7 database. I'm asked for a password when
I make a connection>to the DSN, which I now enter manually.>After that I
can read and write data to the database.>Does anybody know how I can set
the password automatically with the SQL Toolkit>to avoid the dialog ?>
Otherwise
there always has to be a user present when a connection to the>database is
made, which would be very unkomfortable.>Is there any solution ?>>Many thanks
in advance.>Ralf.>

SQL toolkit 2.2 Stored Procedure Memory Leaks

Hi
we are using CVI 2012 and SQL Toolkit 2.2. My db is "MySql 5.5.28" and I use "MySQL Connector/ODBC 5.2(w)"
I use only stored procedure (with and without the output parameters). If I call continuously a stored procedure,
with Sql toolkit code, I have memory leaks!!
My code (without error handler) is:
// iDbConnId is the handle of DBConnect() called when program starts
iStmt = DBPrepareSQL(iDbConnId, "spGetPrData");
DBSetStatementAttribute(iStmt, ATTR_DB_STMT_COMMAND_TYPE, DB_COMMAND_STORED_PROC);
DBExecutePreparedSQL(iStmt);
DBBindColLongLong(iStmt, 1, &llPrId, &lStatus1);
DBBindColInt(iStmt, 2, &iIpPort, &lStatus2);
while(DBFetchNext(iStmt) != DB_EOF)
//get data
DBClosePreparedSQL(iStmt);
DBDiscardSQLStatement(iStmt);
If I call the same stored procedure by sql code ("CALL spProcedure()")
I don't have memory leaks!!
The code is (without error handler):
// iDbConnId is the handle of DBConnect() called when program starts
iStmt = DBActivateSQL(iDbConnId, "CALL spGetPrData();");
DBBindColLongLong(iStmt, 1, &llPrId, &lStatus1);
DBBindColInt(iStmt, 2, &iIpPort, &lStatus2);
while(DBFetchNext(iStmt) != DB_EOF)
//get data
DBDeactivateSQL (iStmt)
It seems to me that the DBDeactivateSQL function free the memory correctly,
while the functions DBClosePreparedSQL and DBDiscardSQLStatement do not release properly the memory,
(or I use improperly the library functions!!!)
I also have a question to ask:
Can I open and close the connection every time I connect to the database or is it mandatory to open and close it just one time?
How can I check the status of the database connection, if is mandatory to open and close the db connection just one time?
Thanks for your help.
Best Regards
Patrizio

Hi,
one of the functions "DBClosePreparedSQL and DBDiscardSQLStatement" is a known problem. In fact, there is a CAR (Corrective Action Request 91490) reporting the problem. What version of the toolkit are you using?
About this function you refer to the manual:
http://digital.ni.com/manuals.nsf/websearch/D3DF4019471D3A9386256B3C006CDC78
Where functions are described. To avoid memory leaks DBDeactivateSQL must be used. DBDeactivateSQL is equivalent to calling DBCloseSQLStatement, then DBDiscardSQLStatement. DBDeativateSQL will work at all for parameterized SQL, as well.
Regarding the connection mode advice to you is to open the connection once and close it at the end of your operations. What do you mean with "state of the database connection"? Remember that if you have connection problems or something goes wrong, the errors appears in any point in your code where you query the database. Bye
Mario

SQL toolkit Win7 connection problem

I'm using CVI 2013 and the SQL toolkit (2.2) tto connect to a mySQL database. I can connect fine using my development computer, but not with the target one. Both computers are running 64-bit Windows 7 Professional (SP1). I was initially using the 64-bit ODBC drivers (mysql-connector-odbc-5.3.2-win64.msi) on both machines. After I had trouble I found a Knowledge Base article that indicated I should probably be using the 32-bit one instead. So I removed the drivers from the target and installed the 32-bit ones using odbcad32.exe found in Windows/SysWOW64. No change.
I'm using the browser2.prj sample project included with the SQL toolkit (by default at: C:\Users\Public\Documents\National Instruments\CVI\samples\sql\apps) to test the functionality of the SQL toolkit. I build a distribution kit including the Shared Run-Time Engine on the development machine and install that on the target. I have traced the problem to the call for DBSources() - it returns a -100 (which, handily, is not amoung the list of database error codes).
On both machines the ODBC drivers appear to be working. I can get to the database using Control Panel->Administrative Tools->Data Sources (ODBC). Selecting the database under either User DSN or System DSN and then clicking Configure will open the MySQL Connector/ODBC Data Source Connection window. Clicking Test in that window will connect to the database.
So the problem seems to lie in the way that CVI connects to the database. I'm clueless at this time, so any suggestions would be greatly appreciated.
Solved!
Go to Solution.

Sorry if this is a stupid question:
Have you followed the instructions in Help->Library Reference->SQL Toolkit Library->SQL Language Reference->Distributing an SQL Toolkit Executable or DLL ?
Or is this an error you are getting despite following those instructions?

What is the equivalent Database Connectivity VI of the SQL Toolkit 'Set SQL Parameter to Null' VI ?

I am using the database connectivity (ADO based) tool and I want to be able to insert a null values.
I have included a simple VI that demonstrates how this works with SQL toolkit .
Null values are very useful and occur frequently in dealing with data. I wish that LabVIEW handled them much better - (e.g. there is not datatype in LabVIEW corresponding to a Null value).

The VI was not attached but I'm going to answer with what I have here.
- Currently, the Database Toolset converts NULLs to the default value for LabVIEW data types (ie, False for Boolean, empty strings, zero for numbers, empty arrays, etc). In the user manual there is an example that shows database records containing NULL values being first converted to a string, empty strings (the NULLs) are then converted to NaNs instead of the usual zero value. This method requires you to know what data types each field contains and that they know what to look for and how to convert the data.
You can go to this following link to suggest that a null datatype be implemented:
https://sine.ni.com/apps/we/nicc.call_me?p_country=&p_lang_id=US&p_form_id=58
-Also you cannot leave par
ameters values empty because there is a big difference between executing an SQL statement and doing a Parameterized Query, especially when looking at the low-level ADO layer.When doing Parameterized Queries, you MUST specify all parameter values - leaving them empty results in ADO trapping errors rather than using a default value.
Regards,
Cyril Bouton
Applications Engineer
National Instruments
Cyril Bouton
Active LabVIEW Developper

Help, Cannot connect to ODBC database using SQL Toolkit!

Hello All,
I am toying around with the SQL Toolkit evaluation (2.2 + the patch) and I am having difficulty.
I ran the example program "connect" and it seems to work fine.
However, I try to write my own program and I keep getting the same message:
"Function DBConnect: (return value == -10 [0xFFFFFFF6]).
Native error code - 2147467259 0x80004005
The message differs from time to time, but the return value is constant.
I am using both Microsoft SQL Server 2012 and MySQL.
For MySQL I have installed the latest ODBC connector, 5.3.4. Inside the Control Panel/Data Sources(ODBC), I have a DSN named test_mysql in both User DSN and System DSN.
I ran a test on the connection and the test passes. I am not sure if I should use the ansi or unicode driver, I have tried both with the same success.
I am not sure I had configured the SQL Server connection properly, and will attempt that again.
My CVI Code is simple enough:
hdbc = DBConnect ("DSN=test_mysql");
Every time I get a -10 from DBConnect. Either I have something configured wrong or I am missing something.
Does anyone have any suggestions?
Veni Vidi Duci
Solved!
Go to Solution.

Update 2:
After getting off the phone with Tech Support the problem has been identified!
LabWindows SQL toolkit requires 32 bit DNS. My PC is a 64 bit, so my DNS manager defaulted to 64 bit.
I needed to use the 32 bit DNS manager when working with the toolkit.
Once I created my DNS connections using the 32-bit version of the ODBC Datga Source manager, everything worked fine.
See this tech note:
http://digital.ni.com/public.nsf/allkb/E7984C0DA0F0E65086257694005B4CB7
Veni Vidi Duci

I want to use the SQL Toolkit of NI and SQL Server as my databasis on a server. Do I need to install a client in each computer I want to handle the data into SQL tables or I need only a ODBC driver?

I want to use the SQL Toolkit of NI and SQL Server as my databasis on a server. Do I need to install a client in each computer I want to handle the data into SQL tables or I need only a ODBC driver?

You only need the ODBC driver on each computer. If you are distributing the SQL Toolkit app as an executable and do not install the whole toolkit on each computer, you'll need the SQL Toolkit support files. This is about a dozen files. You can get the list at http://digital.ni.com/public.nsf/websearch/b814be005f9da9258625658700550c75?OpenDocument.

DBPutRecord Error in SQL Toolkit 2.0 for Mysql

Dear All
I am using Labwindows/CVI 7.1.1 with SQL Toolkit 2.0. I have facing problem in DBPutRecord in database.
First I mapped the Table. While putting Records in table I am facing native Error Code 2147467259.
I can Get the Datas from Table using bound funtion
But Same function and method working fine in CVI 5.5.
Please some one give me the Solution.

kindly refer this and this knowledgebase
Shreyas Hebbare
Shreyas Technologies
India

PL/SQL Toolkit reference manual

Similar Messages

Maybe you are looking for