The default option for maximum nesting level is 16 however this is a server configurable value and can be lesser than this also. To check the current maximum nesting level for stored procedures and tr...

Max nesting level is 16

I think it needs clarification. The only 'workspace' that comes to my mind here is a *.ws file from Sybase Power Designer. In that case a workspace serves as a container for physical, logical ERDs and reports, etc.

The with check option flag prevents insertion or updating of rows that will not meet the view criteria. e.g.: create view cal_publishers_chk as ...

When you create a view using the with check option clause, each insert and update through the view, is validated against the view’s selection criteria. If the rows inserted or updated are out of cri...

You can add a NOT NULL column to a table. This means that a constant expression, and not a null value, is placed in the column when the column is added. This also ensures that, for all existing rows, ...

First add the column as NULL. Then populate the column with non-null data. Then modify the column to NOT NULL. You may need to set dboption "select into" to True.

That is a vendor-specific question.In Sybase, you can get log file information as follows:prompt$ isql1> sp_help {database} 2> goThat will list the devices used by the database, including log de...

Sybase does support locking at row level in version 12.5 onwards.

Sybase use locking in below modes
- Shared
- Exclusive
- Update

For APL(all page locking), sybase locks data as well index page
For DOL(data only locks) either row level or data page level, sybase use not transactional locking(latches)

Lock: controling access to page
In sybase, locking is done at page level (whereas in Oracle, it is at row level).
So, suppose if we have a lock (shared lock, write lock) on a page, than we can not access any rows in that page.