09-15-2009
Remover Banner and SQL prompt from isql
Hi,
I am using isql and putting the output in a file in a shell script in Linux.
However in my output i am getting the banner and a SQL prompt(at the start and the end of query output)
+---------------------------------------+
| Connected! |
| |
| sql-statement |
| help [tablename] |
| quit |
| |
+---------------------------------------+
SQL>query output
SQL>
I need just the query result
Any ideas on how to acheive this?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hey all,
I want to use the banner/echo command to write messages on different console windows.
I knew that before, but I completely forget how to do it ! I just remenber that /dev/pts/# is the number of the window. and it's useful.
It would be great if someone knows how to solve my... (4 Replies)
Discussion started by: maxwell17
4 Replies
2. UNIX for Dummies Questions & Answers
How can I display a message to the crt whenever someone logs on? They do not see a unix prompt. I need to easily update this also. (2 Replies)
Discussion started by: Beetlejuice
2 Replies
3. Solaris
After dumping data from an Oracle database running on Solaris into a flat file, we need to run bcp and isql for MS SQL Server on the same Solaris box. Does Microsoft provide some tools that run on Unix?
Thanks for your assistance. (2 Replies)
Discussion started by: tomstone_98
2 Replies
4. Shell Programming and Scripting
I've got:
isql -U $USERID -S $SERVER -D $DATABASE -i inputfile.sql -o outputfile.txt
in inputfile I have:
go
sql#1
go
sql#2
go
sql#3
go
I also tried without "go" and with";" instead which did not work
SQL statements will work if I paste them directly into the script and use EOF
... (0 Replies)
Discussion started by: Cailet
0 Replies
5. Shell Programming and Scripting
This is not a typical question. I have a fully working script but I'm interested in optimizing it.
I frequently back up photos and movies from my digital camera and cell phone to both my home/work desktops, laptops, wife's netbook, and my home NAS and often end up with multiple versions of the... (2 Replies)
Discussion started by: Michael Stora
2 Replies
6. Shell Programming and Scripting
Hi All,
I have a doubt whether expect module in perl will work in SQL prompt or its applicable only for shell prompt ?
Thanks,
Arun V (2 Replies)
Discussion started by: arun_maffy
2 Replies
7. UNIX for Dummies Questions & Answers
is there a way to reduce the size of the banner?
banner -w ?
TIA (8 Replies)
Discussion started by: budz26
8 Replies
8. UNIX for Dummies Questions & Answers
how to Change the % prompt to - prompt in unix
:wall:
---------- Post updated at 07:40 AM ---------- Previous update was at 07:38 AM ----------
How To display the last modification time of any file in unix
---------- Post updated at 07:40 AM ---------- Previous update was at 07:40 AM... (2 Replies)
Discussion started by: manjiri sawant
2 Replies
9. Solaris
Hi,
on sunfire v890 unable to move from rsc prompt to ok prompt, i have executed the command break. (9 Replies)
Discussion started by: manoj.solaris
9 Replies
10. Shell Programming and Scripting
need to create shell script to read the table's name from file and connect SQL SERVER using isql (odbcunix)
i 'm able connect to database with below command line syntex but i could not get working in shell script with SQL and storing the row count in variable.
isql -v DSN USERNAME PASSWD
... (6 Replies)
Discussion started by: pimmit22043
6 Replies
LEARN ABOUT REDHAT
prepare
PREPARE(7) SQL Commands PREPARE(7)
NAME
PREPARE - create a prepared query
SYNOPSIS
PREPARE plan_name [ (datatype [, ...] ) ] AS query
INPUTS
plan_name
An arbitrary name given to this particular prepared query. It must be unique within a single session, and is used to execute or
remove a previously prepared query.
datatype
The data-type of a parameter to the prepared query. To refer to the parameters in the prepared query itself, use $1, $2, etc.
OUTPUTS
PREPARE
The query has been prepared successfully.
DESCRIPTION
PREPARE creates a prepared query. A prepared query is a server-side object that can be used to optimize performance. When the PREPARE
statement is executed, the specified query is parsed, rewritten, and planned. When a subsequent EXECUTE statement is issued, the prepared
query need only be executed. Thus, the parsing, rewriting, and planning stages are only performed once, instead of every time the query is
executed.
Prepared queries can take parameters: values that are substituted into the query when it is executed. To specify the parameters to a pre-
pared query, include a list of data-types with the PREPARE statement. In the query itself, you can refer to the parameters by position
using $1, $2, etc. When executing the query, specify the actual values for these parameters in the EXECUTE statement -- refer to EXECUTE
[execute(7)] for more information.
Prepared queries are stored locally (in the current backend), and only exist for the duration of the current database session. When the
client exits, the prepared query is forgotten, and so it must be re-created before being used again. This also means that a single prepared
query cannot be used by multiple simultaneous database clients; however, each client can create their own prepared query to use.
Prepared queries have the largest performance advantage when a single backend is being used to execute a large number of similar queries.
The performance difference will be particularly significant if the queries are complex to plan or rewrite. For example, if the query
involves a join of many tables or requires the application of several rules. If the query is relatively simple to plan and rewrite but rel-
atively expensive to execute, the performance advantage of prepared queries will be less noticeable.
NOTES
In some situations, the query plan produced by PostgreSQL for a prepared query may be inferior to the plan produced if the query were sub-
mitted and executed normally. This is because when the query is planned (and the optimizer attempts to determine the optimal query plan),
the actual values of any parameters specified in the query are unavailable. PostgreSQL collects statistics on the distribution of data in
the table, and can use constant values in a query to make guesses about the likely result of executing the query. Since this data is
unavailable when planning prepared queries with parameters, the chosen plan may be sub-optimal.
For more information on query planning and the statistics collected by PostgreSQL for query optimization purposes, see the ANALYZE [ana-
lyze(7)] documentation.
COMPATIBILITY
SQL92
SQL92 includes a PREPARE statement, but it is only for use in embedded SQL clients. The PREPARE statement implemented by PostgreSQL also
uses a somewhat different syntax.
SQL - Language Statements 2002-11-22 PREPARE(7)