鏃ュ父瑕佺洃瑙嗙殑涓昏鐩爣鏈夛細鐢ㄦ埛鏁版嵁搴撱佹暟鎹簱鏃ュ織琛紙syslogs錛変互鍙婅璐瑰師濮嬫暟鎹〃絳夈傚鏋滃彂鐜板崰鐢ㄧ┖闂磋繃澶э紝瀵規棩蹇楄〃瑕佽繘琛岃漿鍌紱瀵瑰叾浠栫洰鏍囧垯搴旀墿鍏呯┖闂存垨娓呮鍨冨溇鏁版嵁銆?br />
3錛夈佺洃瑙?SQL Server 緇熻鏁板瓧
浣跨敤緋葷粺榪囩▼錛歴p_monitor
璇存槑錛歴p_monitor 鏄劇ずSQL Server 鐨勫巻鍙茬粺璁℃暟瀛楋紝涓嬭〃鏄煇緋葷粺鐨勭粺璁℃暟瀛楋細
18.鍒涘緩鐢ㄦ埛鏁版嵁搴?br />
浠ヤ笅閫氳繃涓涓緩绔嬫暟鎹簱鐨勮剼鏈鏄庡緩绔嬫暟鎹簱鐨勮繃紼嬶細
//鍒涘緩鏁版嵁搴撹澶囷紝璁懼澶у皬浠ラ〉錛?K錛変負鍗曚綅
disk init
name="test_dbdev",
physname="/home/bk/test_dbdev.dat",
vdevno=5,
size=10240
go
disk init
name="test_logdev",
physname="/home/bk/test_logdev.dat",
vdevno=6,
size=5120
go
//鍒涘緩鏁版嵁搴揟EST_DB錛屽叾澶у皬涓?0M錛屾棩蹇楀ぇ灝忎負10M
create database TEST_DB
on test_dbdev=20
log on test_logdev=10
go
//鎵撳紑鏁版嵁搴?br />
use TEST_DB
go
-----------
涓句緥璇存槑錛?br />
DISK INIT
Name=’My_Device’,
Physname=’D:\database\My_device.dat’,
Vdevno=3
Size=5000
娉ㄩ噴錛氶昏緫鍚嶃佺墿鐞嗗悕銆佽澶囪櫄鎷熷彿銆佽澶囧ぇ灝?br />
------------------------
鍒涘緩鐢ㄦ埛鏁版嵁搴?br />
Create Database 鏁版嵁搴撳悕
On 璁懼_1=Size_1,//鍗曚綅錛歁
璁懼_2=Size_2,
……
log on 鏃ュ織璁懼=Log_Size
[With Override]//鍦ㄥ悓涓璁懼涓婂垱寤烘暟鎹簱鍜屼簨鍔℃棩蹇楁椂浣跨敤璇ラ夐」
[For Load] //紱佹鐢ㄦ埛璁塊棶鐩村埌鏁版嵁搴撶殑瑁呭叆鎴栨仮澶嶆搷浣滃畬鎴愪負姝?br />
涓句緥錛?br />
Create Database test_db
On data_dev=100,//鍗曚綅錛歁
Index_dev=50
Log on log_dev=30
璇存槑錛?br />
錛?錛夊皢鏃ュ織鏀懼湪鍗曠嫭鐨勮澶囦笂錛屾湁鍒╀簬鏁版嵁搴撴ц兘鐨勬彁楂橈紱
錛?錛夊鏋滃皢鏁版嵁搴撳拰鏃ュ織鏀懼湪鍚屼竴璁懼涓婏紝灝變笉鑳藉疄鐜板閲忓浠斤紱
錛?錛夐氬父灝哠ystem鍜孌efault孌電緝鍑忚寖鍥村埌涓涓澶囦笂錛屽鍒犻櫎璁懼Index_dev涓婄殑System孌靛拰Default孌碉紝鍒涘緩鏂扮殑孌碉紝鐢ㄦ潵瀛樻斁涓撻棬鐨勬暟鎹簱瀵硅薄
19.澶囦喚鍜屾仮澶岲B鏁版嵁
dump database mydb to '/u01/mydb_full.bk'
go
dump tranaction mydb to '/u01/mydb_tran.bk'
go
load database mydb from '/u01/mydb_full.bk'
load transaction mydb from '/u01/mydb_tran.bk'
online database mydb
go
ps:閲囩敤澧為噺澶囦喚鍚庯紝涓ョ鏃ュ織鎴柇! 鍗崇姝嬌鐢細dump transaction sctf truncate_only 鍛戒護!
澧為噺澶囦喚蹇呴』鏄湪瀹屾暣澶囦喚鍚庣殑鎴栦笂涓嬈″閲忓浠藉悗錛屼腑闂磋嫢閬囧埌鏃ュ織鎴柇錛屽悗緇殑澧為噺澶囦喚鍧囧憡澶辮觸錛?br />
澧為噺澶囦喚鍙互鏍規嵁闇瑕侊紝濡傛瘡灝忔椂澶囦喚涓嬈★紝姣忔澶囦喚鎵闇鏃墮棿綰?錛?縐掞紝鎵浠ユ椂闂存瀬蹇?br />
ps: 鍗曞紩鍙峰拰鍙屽紩鍙烽兘鑳藉叧闂璼hell瀵圭壒孌婂瓧絎︾殑澶勭悊銆備笉鍚岀殑鏄紝鍙屽紩鍙鋒病鏈夊崟寮曞彿涓ユ牸錛屽崟寮曞彿鍏抽棴鎵鏈夋湁鐗規畩浣滅敤鐨勫瓧絎︼紝鑰屽弻寮曞彿鍙姹俿hell蹇界暐澶у鏁幫紝鍏蜂綋鐨勮錛屽氨鏄憼緹庡厓絎﹀彿鈶″弽寮曞彿鈶㈠弽鏂滄潬錛岃繖3縐嶇壒孌婂瓧絎︿笉琚拷鐣ャ?涓嶅拷鐣ョ編鍏冪鍙鋒剰鍛崇潃shell鍦ㄥ弻寮曞彿鍐呴儴涔熻繘琛屽彉閲忓悕鏇挎崲銆?br />
*********************************************
涓嬮潰璧勬枡鏉ヨ嚜SYBASE鐧界毊涔?br />
1銆傚鎴風瀛楃闆嗕慨鏀?locales.dat
2.鍙互閫氳繃璁劇疆CHARSET椹卞姩紼嬪簭灞炴ф寚瀹氬湪搴旂敤紼嬪簭涓嬌鐢ㄧ殑瀛楃闆嗐?br />
鎴栬呰緗甹connect瀛楃闆嗙殑鏂規硶鏉ヨ緗?br />
3銆傛煡鐪嬪瓧絎﹂泦錛?br />
SERVER錛歴p_helpsort
go
CLIENT錛歴elect @@client_csname
go
4.孌?闃鍊鹼細
榛樿鏄笁涓: system default logsegment
system孌? 鏁版嵁搴撶郴緇熻〃瀛樻斁澶?br />
default孌? 鏈寚鏄庢鐨勫璞¢兘瀛樻斁鍦ㄨ繖閲?br />
logsegment孌?鏁版嵁搴撶殑浜嬪姟鏃ュ織瀛樻斁澶?br />
闃鍊?threshold) :
寤虹珛闃鍊? sp_addthreshold 搴撳悕,孌靛悕,鑷敱絀洪棿,瀛樺偍榪囩▼鍚嶅瓧
鍒犻櫎闃鍊? sp_dropthreshold 搴撳悕,孌靛悕,鑷敱絀洪棿欏?
鏄劇ず闃鍊? sp_helpthreshold
綆$悊闃鍊? sp_dboption
鏄劇ず孌電┖闂翠俊鎭?sp_helpsegment
闃鍊肩鐞嗙殑嫻佺▼濡備笅:
鍏堝緩瀛樺偍榪囩▼:(涓嬮潰鐨勬槸鏃ュ織鐨勫瓨鍌ㄨ繃紼?鍘熷洜:鏃ュ織澧為暱鍏鋒湁涓嶅彲棰勮鎬?鐩告瘮涔嬩笅,鏁版嵁澧為暱鍏鋒湁鍙瑙佹?鎵浠ヤ竴鑸兘寤簂ogsegment鐨勯榾鍊肩鐞?default鐨勯榾鍊肩鐞嗗彲涓嶅緩)
create procedure szjj
@dbname varchar (30),
@segmentname varchar (30),
@space_left int,
@status int
as
dump transaction @dbname to "/tmp/bb.dat"
go
ps:涓婇潰鏄棩蹇楃殑瀛樺偍榪囩▼,濡傛灉鏄暟鎹殑瀛樺偍鍒欑敤dump database...
鏌ョ湅褰撳墠鏃ュ織鑷敱絀洪棿鎯呭喌:
sp_helpsegment logsegment
go
鏌ョ湅褰撳墠鏁版嵁搴撴暟鎹嚜鐢辯┖闂存儏鍐?
sp_helpsegment default
go
鏌ョ湅褰撳墠闃鍊兼儏鍐?
sp_helpthreshold
go
鏌ョ湅褰撳墠孌墊儏鍐?
sp_helpsegment
go
鐒跺悗鏍規嵁鑷敱絀洪棿鏉ュ畾闃鍊煎弬鏁?
sp_addthreshold test_db,logsegment,200,szjj
go
ps:褰撴棩蹇楁鐨勬渶鍚庢満浼氶榾鍊艱瓚呰秺鍚?璇曞浘寰璇ユ棩蹇楁涓婅鏃ュ織鐨勭敤鎴瘋繘紼嬮粯璁ゆ槸琚寕璧?鐢ㄤ笅闈㈢殑鍛戒護淇敼MASTER搴撳弬鏁?璁╅榾鍊艱瓚呰秺鍚庝簨鍔″氨浼氭粴.
use master
go
sp_dboption test_db,"abort tran on log full",true
go
5.緇存姢
1錛夊鍚凙SE鐢ㄦ埛鎷呭綋鐨勮鑹插拰鐗規潈榪涜鍒嗘淳銆?br />
2錛夌鐞嗗拰鐩戣紓佺洏絀洪棿鐨勪嬌鐢ㄦ儏鍐點?br />
3錛夋暟鎹簱絀洪棿錛?br />
sp_helpdb 鏌ョ湅鍚勫簱鎯呭喌
alter database 鎵╁厖絀洪棿
dump tran 鎴柇鏃ュ織
4錛夋棩甯告暟鎹浠藉拰鎭㈠
5錛塖YBASE榛樿鐨勬湇鍔″櫒錛?br />
adaptive server:綆$悊鏁翠釜鏁版嵁搴撶郴緇燂紝鍖呮嫭鐢ㄦ埛 鏁版嵁 璧勬簮絳夌殑綆$悊鍜屾帶鍒躲?br />
backup server: 鍦ㄥ浠藉拰鎭㈠鏃舵墽琛屾暟鎹簱鐨刣ump or load
xp server:鎵ц鎵╁睍瀛樺偍榪囩▼
monitor server:涓烘ц兘璋冭瘯鍒嗘瀽閲囬泦鏁版嵁銆?br />
historical server:淇濆瓨鏉ヨ嚜monitor server鐨勬暟鎹紝浠ュ灝嗘潵鍒嗘瀽銆?br />
6銆傚崟妯″紡鍚姩SYBASE
1錛夊仠姝SE鏁版嵁搴撴湇鍔?br />
2錛?/install/startserver -f RUN_servername -m
ps:windows涓嬪湪鏈嶅姟鐨勫睘鎬ч噷鍔?m銆?br />
7.license搴忓垪鍙?br />
楠岃瘉璁稿彲杞歡鏄惁鎵ц:*/bin/lmutil lmstat -c
鎵嬪伐鍚姩:*/bin/lmgrd -c $lm_license_file&
鍚姩璁稿彲綆$悊鍣細*/bin/lmgr
榪愯錛?/bin/lmutil lmreread
8.鏌ョ湅閫昏緫欏靛ぇ灝?br />
select @@maxpagesize
9.鍚姩鍏抽棴SYBASE
鍚姩錛?/startserver -f RUN_servername
鍏抽棴錛氱櫥褰曞悗shutdown鍏蟲暟鎹簱鏈嶅姟 shutdown SYB_BACKUP鍏沖浠芥湇鍔″櫒
10銆傚笎鎴風鐞?br />
SA甯愭埛鍒濆鍙d護涓虹┖錛屽叿鏈塖A鍜孲SO瑙掕壊銆傚叿鏈塖SO鐨勭櫥褰曞笎鎴峰彲浠ユ坊鍔犲叾浠栫櫥褰曞笎鎴楓?br />
1錛夊垱寤虹櫥褰曞笎鎴?br />
sp_addlogin login_name,password
go
2)淇敼甯愭埛瀵嗙爜
sp_password caller_password,new_password,login_name
go
3)璁劇疆鐧誨綍甯愭埛鐨勭己鐪佹暟鎹簱(濡傛灉涓嶆寚瀹?榛樿鏄痬aster搴?
sp_addlogin login_name,password,default_db
go
or
sp_modifylogin login_name,"defdb",db_name
go
4錛変負鐧誨綍甯愭埛鎺堜簣緋葷粺瑙掕壊
sp_role "grant",role_name,login_name
go
or
grant role role_name to login_name
go
5)鏌ョ湅鐧誨綍甯愭埛鐨勪俊鎭?br />
sp_displaylogin login_name
go
6)SYBASE甯哥敤瑙掕壊錛歴a sso oper
7)淇敼鐧誨綍瀵嗙爜
sp_password caller_passwd,new_passwd[,login_name]
8)鍒犻櫎sa_role鐨勫彛浠?br />
alter role sa_role drop passwd
9錛夊垱寤烘暟鎹簱鐢ㄦ埛
sp_adduser loginname[,name_in_db[,grpname]]
go
10)娣誨姞鐢ㄦ埛騫舵巿浜堟煡璇㈡潈闄?br />
sp_adduser 鏉冮檺 on 琛ㄥ悕 to 鐢ㄦ埛鍚?br />
11錛夊垹闄ゅ埆鍚?br />
sp_dropalias loginname
12)鍒涘緩鐢ㄦ埛鑷畾涔夌粍
sp_addgroup grpname
go
13)鎵懼洖SA瀵嗙爜
鍋滄SYBASE鏈嶅姟--銆変慨鏀筊UN_xxx,鍦ㄥ懡浠よ鐨勬渶鍚庡姞涓?psa--銆塻tartserver -f RUN_xxx-->鍚姩淇℃伅鐨勬渶鍚庝細鍑烘潵瀵嗙爜銆?br />
11銆傛暟鎹簱綆$悊
1錛夋暟鎹簱閫夐」鐨勮緗?br />
sp_dboption[dbname,optname,{,true|false}]
2)寤哄簱
create database dbname on data_device_name=size log on log_device_name=size
go
ps:size default is M
3)鏌ョ湅搴撳ぇ灝?sp_helpdb dbname
4)鏀瑰彉搴撶殑灞炰富 sp_changedbowner loginname[,true]
5)鎵╁睍鏁版嵁搴?br />
鎵╁睍鏁版嵁絀洪棿錛歛lter database db_name on device_name
鎵╁睍鏃ュ織絀洪棿: alter database db_name log on device_name
6)璁劇疆鏁版嵁搴撲負鍗曠敤鎴鋒ā寮?鍙互鍦ㄧ敤鎴瘋〃涓嚜鍔ㄦ坊鍔犲簭鍙風敓鎴愬櫒/鑷姩鎴柇浜嬪姟鏃ュ織妯″紡
use master
go
sp_dboption db_name,"signle user",true
go
sp_dboption db_name,"trunc log on chkpt",true
go
sp_dboption db_name,"auto identity",true
use db_name
go
checkpoint
go
7)鏌ョ湅褰撳墠搴撶殑榪涚▼淇℃伅
sp_who
闄勫綍=====================================
Explanation
SQL commands are grouped into the following categories:
SQL commands that are not allowed in transactions at all.
SQL commands, such as Data Definition Language (DDL) commands, that are allowed in transactions only if the required database option (ddl in tran) is set to TRUE.
SQL commands that are allowed only if the transaction affects some other database. These commands include create table, drop table, and other commands that are run across databases to create or drop objects in another database when the database in which the objects are being created or dropped has the database option ddl in tran set to TRUE.
Error 226 occurs when Adaptive Server detects a command that is not allowed in a multi-statement transaction. A multi-statement transaction is a set of commands prefaced with the begin transaction command.
The following commands are never allowed in multi-statement transactions:
alter database
create database
dbcc reindex, dbcc fix_text
disk init
drop database
dump database, dump transaction
load database, load transaction
select into
set transaction isolation level
truncate table
update statistics
setuser
The following commands are not normally allowed in multi-statement transactions but you can use them if you use sp_dboption to set ddl in tran to TRUE first:
create default
create index
create procedure
create rule
create schema
create table
create trigger
create view
drop default
drop index
drop procedure
drop rule
drop table
drop trigger
drop view
grant
revoke
Action
If the command is allowed in a multistatement transaction when ddl in tran is set to TRUE, set ddl in tran to TRUE before running the transaction. Setting ddl in tran to TRUE causes locks on system tables and this can affect performance. You can check the current setting of ddl in tran with sp_helpdb.
If the command is never allowed in a multi-statement transaction, execute it outside the multi-statement transaction.