1. Visit this page
__ https://help.sap.com/viewer/product/SAP_ASE/16.0.4.0/en-US?task=whats_new_task
2. Select [ Download PDFs ] at top right
3. Choose the manuals you want, and download them.
Feel free to ask me questions.
On Wednesday, 4 August 2021 at 21:21:38 UTC+10, Nicola wrote:
I am starting a separate thread about this:
1. Visit this page
__ https://help.sap.com/viewer/product/SAP_ASE/16.0.4.0/en-US?task=whats_new_task
2. Select [ Download PDFs ] at top right
3. Choose the manuals you want, and download them.
Thanks, got them already.
Feel free to ask me questions.
What page size (2/4/8/16 KB) and what type of workload (Mixed/OLTP)
do you configure?
What are the strictly technical reasons to prefer ASE over SQL Server?
Or SQL Server over ASE?
How about this historical assessment:
https://dbdb.io/db/adaptive-server-enterprise
Buggy release, mismanagement… Doesn't sound like a product to go after ;-)
On Thursday, 5 August 2021 at 12:56:18 UTC+10, Derek Ignatius Asirvadem wrote:
On Wednesday, 4 August 2021 at 21:21:38 UTC+10, Nicola wrote:
What page size (2/4/8/16 KB) and what type of workload (Mixed/OLTP)
do you configure?
On the other hand, if you have a specific question re your stated project, I would be happy to help. No discussion, just the answer.
if I rephrase your question such that it is pertinent and direct, such
as:
< < What page size (2/4/8/16 KB) do you recommend that I configure ?
Because this is a permanent physical article, that precedes
installation, for what I expect is best for you, eg. I expect you to
stress the server with benchmarks and large Transactions, as well as
a mixed OLTP+OLAP load = 4KB.
If you are on Unix/Linux, make sure you create only Raw Partitions for
all Devices, never filesystem files.
On Sunday, 8 August 2021 at 22:24:39 UTC+10, Nicola wrote:
On 2021-08-06, Derek Ignatius Asirvadem wrote:
if I rephrase your question such that it is pertinent and direct, such
as:
< < What page size (2/4/8/16 KB) do you recommend that I configure ?
Because this is a permanent physical article, that precedes
installation, for what I expect is best for you, eg. I expect you to stress the server with benchmarks and large Transactions, as well as
a mixed OLTP+OLAP load = 4KB.
Ok, thanks. I had inferred from your documents that your benchmarks were done on systems configured with 2 KB pages,
so I was wondering whether
(that is the case and)
you had a point to always prefer smaller
pages to larger ones.
Because this is a permanent physical article, that precedes
installation, for what I expect is best for you, eg. I expect you to stress the server with benchmarks and large Transactions,
as well as
a mixed OLTP+OLAP load = 4KB.
On Sunday, 29 August 2021 at 04:46:23 UTC+10, Nicola wrote:
Derek,
I've gone full speed with some benchmark scripts up and running
against
a pretty default ASE installation.
I have created two devices, one for
databases ("userdbdev") and one for the transaction log ("userlogdev").
My test database was created with:
create database scratch on userdbdev = '1g' log on userlogdev = '1g'
After several runs of my scripts,
I have started to get this error:
The transaction log in database scratch is almost full. Your transaction
is being suspended until space is made available in the log.
1. How do I flush the transaction log?
“flush”
-- [A] Proper manual DB-DUMP, file_path needs to have space-used-in-db
DUMP DATABASE <db_name> to <db_file_path>
GO
-- [B] Proper manual TRAN-DUMP (very first step for understanding):
-- file_path needs to have space-used-in-tran-log
DUMP TRAN <db_name> to <log_file_path>
GO
-- [C] When you get 1105 or “log suspended”, it is usually too late, so you need:
DUMP TRAN <db_name> WITH TRUNCATE_ONLY
-- or worse:
DUMP TRAN <db_name> WITH NO_LOG
GO
-- [D] Development db: set db_name to TRUNCATE tranlog automatically
-- tranlog can be very small
USE userdbdev
GO
master..sp_dboption userdbdev, "trunc log on chkpt", true
GO
CHECKPOINT
GO
2. How do I monitor the size of the transaction log?
USE <db_name>
GO
sp_helpdb <db_name>
GO
sp_helplog
sp_helpsegment -- without parms
sp_helpsegment logsegment
sp_helpthreshold -- without parms
sp_helpthreshold logsegment
3. How do I avoid the above message in the first place?
a pretty default ASE installation.
On Sunday, 29 August 2021 at 12:53:00 UTC+10, Derek Ignatius Asirvadem wrote:
On Sunday, 29 August 2021 at 04:46:23 UTC+10, Nicola wrote:
create database scratch on userdbdev = '1g' log on userlogdev = '1g'
c. for a benchmark or production you need an purpose-written sp (because it uses site-specific resources and setting)
d. I have high-activity Production dbs with 500gb data and 100mb tran-log. Ie. the tran-log size is dependent on (i) activity, and (ii) max tran size [which should be small], and (iii) how it gets dumped, which is that sp.
But you are much better off defining DUMP-DEVICES.determination. Eg. for tempdb, I TRUNCATE; for production I DUMP, for emergency in tempdb, I kill tasks (which clears their data usage).
-- [C] When you get 1105 or “log suspended”, it is usually too late, so you need:
DUMP TRAN <db_name> WITH TRUNCATE_ONLY
-- or worse:
DUMP TRAN <db_name> WITH NO_LOG
GO
Which clears the 1105 or “log suspend”, but now recovery on that db is from a DB-dump-file only. So you must DUMP DATABASE to produce a fresh one.
==[E] Set up any db (C) to be automatically tran-log dumped when “full”. That means thresholds on the logsegment, and a threshold stored proc to be executed when the threshold is reached. There can be more than 1 threshold, more than one escape
sp_helpthreshold -- without parms
sp_helpthreshold logsegment
You have to take responsibility as a Sybase DBA (welcome to the club).
Any and all config and settings re recovery must be made explicitly.
Generally, you have to set up, in this order:
1. think about how you want your DATA vs LOG distributed.
2. think about how you want your RECOVERY to be done (Dev vs Benchmark vs Production).
3. set up DEVICES accordingly
__ I recommend (instead of your 100gb), which must be RAW PARTITIONS (not filesystem-files):
____ 8 x 128MB for DATA (for parallelism)
____ 1 x 128MB for Non-Clustered Indices
____ 1 x 128MB for TRAN-LOG for EACH database SEPARATELY
4. set up your DATABASES accordingly, ala sp_dboption
5. either
__ (D) no recovery (Dev: TRUNC-LOG-ON-CHKPT) or
__ (A) reasonable recovery (Benchmark) or
__ (B) minimum-production-recovery (Production)
6. for (A)(B), set up a threshold at least on the logsegment, to automatically DUMP TRAN
sp_helplog
sp_helpsegment -- without parms
sp_helpsegment logsegment
sp_helpthreshold -- without parms
sp_helpthreshold logsegment
----manager”, look for it.
General
1. For admin tasks, most people use a 3rd party DBA Admin tool, such as DBArtisan.
Sybase does have a free DB Admin tool, free with a licence for ASE, a very nice GUI (not as amazing as DBArtisan which I have), but I don’t know if it is included in the dev version (“express edition”). It is called something like “enterprise
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 349 |
Nodes: | 16 (0 / 16) |
Uptime: | 146:49:33 |
Calls: | 7,614 |
Calls today: | 2 |
Files: | 12,792 |
Messages: | 5,685,002 |
Posted today: | 2 |