Doubts in IDS 2000
William Raper
Rajesh
Here are the answers to your questions.
1. Space Restriction / User Quotas ---- no
2. Database Logging
My opinion is that unbuffered logging is the best, as long as the
activity on your system will not conflict with the disk writes. If there is
a serious conflict, you can consider buffered logging, as long as the
performance need outweighs the data-loss risk if your server crashes.
ANSI logging has one advantage: implicit transactions - all SQL
statements are logged, so you can do a rollback without having used a "begin
work" command.
ANSI disadvantages
(1) committed read isolation level by default (results in MANY rows
locked for (clockwise) long-running queries that select a large number of
rows (e.g. any kind of DSS report can lock all rows that it touches)
(2) once a database has been set to ANSI logging, it cannot be changed
back to either unlogged or buffered/unbuffered logging without unloading,
dropping, recreating and reloading your database
In a nutshell - ANSI should only be used when there is some EXTERNAL
driver that enforces it (e.g. externally driven technical requirements)
3. To get the DDL of a table:
from UNIX prompt type: dbschema -d <database name> -t <table name>
<output filename>
This will create a file with the COMPLETE DDL for your table
This tool can further be used to get the full DDL of your database,
tables, indexes, primary/foreign keys, triggers, and stored procedures
(let's see Oracle touch that one!!!)
4. Running an SQL command from a prompt:
dbaccess <database name> <script name>
<<< OR >>>
echo "sql statement" | dbaccess <databasename>
5. IECC
You are short-on-luck on this one. Informix has decided to abandon this
product. Watch this fall for "Server Studio Java Edition", which is
currently in beta testing, or for a little over $900 per seat you can get
Server Studio from http://www.agsltd.com
-----Original Message-----
From: leo...@isg-india.com [mailto:leo...@isg-india.com]
Sent: Friday, July 27, 2001 8:50 AM
To: inform...@iiug.org
Subject: Doubts in IDS 2000
Hi,
I have the following doubts in Informix IDS2000. Kindly help me.
1. Is there any way to restrict a user in terms of dbspace usage / disk
space usage.
Can i restrict the user to use only certain amount of diskspace. (Quota
restriction)
2. What is the best method of logging u can use in ur database.
I feel for a online system, Unbuffered logging is the best one.
Please tell me about the PRACTICAL adv & dis adv about ANSI databases.
3. I want to know is there any option availabile in Informix to get the
descriptive info of columns (table structure).
(In oracle there is a feature called data dictionary, the command desc
table_name will give you the table structure)
U can get the same information from the syscolumns system catalog table but
all these informations are available in the codified form. There is no
descriptive information for datatype, size etc . Is there any built in
functions available to get the descriptive information of the table
structures.
4. Is there any tool available in UNIX to run the sql statments like sql
editor or in a prompt. (In oracle , u are typing the sql statments in the
sql prompt and executing the stmts. )
5. Do u need to buy IECC separetly. Is that not a part of the database
server kit.
I doubt, whether IECC is available for SCO unix ware 7.x
Expecting ur early reply with solutions
Thanks & Regards
Rajesh
India Software Group
Chennai, India.