NICE TO HAVE FEATURES

[Eddie_A]

1 - A system table that records info from errorlog
-- you don't need a sybase account just to read the /opt/sybase/ase-*/
install/errorlog

2 - create database mydb on mydev_dat("/opt/sybase/data/mydb.dat")
="1000m"
log on mydev_log("/opt/sybase/
data/mydb.log")="500m"
-- The shortcut way creating both db and device -- (other RDBMS
already have this feature)

3 - set forcereadisk on - turns on to force the server to read from
disk instead of cache for debugging and optimization purposes

[Rob V [ Sybase ]]

Just commenting on #1: this is already possible in two different ways:

(i) you can define a proxy table mapping to the errorlog file, so you can
read it by querying the proxy table. This is pretty simple (also see section
2.3.5 of my book "Tips, Tricks & Recipes for Sybase ASE" should you have
that)

(ii) the MDA table monErrorLog contains the last N lines written to the
errorlog (N is configurable).

HTH,

Rob V.
-----------------------------------------------------------------
Rob Verschoor

Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
and Replication Server 15.0.1/12.5 // TeamSybase

Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks & Recipes for Sybase ASE" (ASE 15 edition)
"The Complete Sybase ASE Quick Reference Guide"
"The Complete Sybase Replication Server Quick Reference Guide"

mailto:r...@YOUR.SPAM.sypron.nl.NOT.FOR.ME
http://www.sypron.nl
Sypron B.V., Amersfoort, The Netherlands
Chamber of Commerce 27138666
-----------------------------------------------------------------

"Eddie_A" <renzo....@gmail.com> wrote in message
news:e6e375fd-c574-4666...@f16g2000yqm.googlegroups.com...

[Carl Kayser]

"Eddie_A" <renzo....@gmail.com> wrote in message
news:e6e375fd-c574-4666...@f16g2000yqm.googlegroups.com...

(1) Apparently you meant "you don't need an OS account ..." And Rob
provided two solutions for this functionality. (I agree with the feature
intent and personally use the RPC solution for this functionality.)

(2) This brings up a problem in my mind. The sizes are for both the
database and the device. If you have a limited number of OS partitions (as
I do with Solaris) and many databases (250+ on one of my ASE servers) then
this feature won't really buy you anything. I also like to see how the
space is allocated on devices used for ASE. This includes "device free
space" which I can't see from within ASE using the above shortcut.

(3) Interesting. I can see the tuning possibility but don't see the
debugging aspect. Could you provide a particular example? What happens at
the end of the set forcereadisk command /batch/session? I'm guessing that
the data is discarded else you have two versions of the same data - a DBA
no-no.

[Carl Kayser]

"Carl Kayser" <kays...@bls.gov> wrote in message
news:4b0fc042$1@forums-1-dub...

Ahh, headaches with (1). Only an SA granted mon_role can select from the
monErrorLog table; this can't be overriden. Using the RPC technique could
open up some security concerns with xp_cmdshell.

[Eddie_A]

On Nov 28, 3:47 am, "Carl Kayser" <kayse...@bls.gov> wrote:
> "Carl Kayser" <kayse...@bls.gov> wrote in message
>
> news:4b0fc042$1@forums-1-dub...
>
>
>
>
>
> > "Eddie_A" <renzo.aqu...@gmail.com> wrote in message

Reasons:
Feature 1- In my experience as a DBA I don't care about all about
these things. But now I am on a different project were I don't have
access to the errorlog. It brought me to realize that as an ordinary
user am just left out with nothing if I get a message "ASE is
terminating this process" or a process just went dead or something. It
would be nice if there is something I can look at the errors

Feature 2- This would be just an added feature to what is already
there. In cases were you have limited partitions, you can use the old
method. Why would you sacrifice a nice feature just because because
one OS will not benefit from it.

Feature 3- Again as an ordinary user you don't have all the tuning
rights of a DBA in optimizing an SQL. You cannot unbind a cache, etc.
So don't blame the SQL Dev or DEV DBA for a slow running SQL. This
feature will primarily be for tuning purposes only. What is on the
cache don't touch it, just read it from the disk.