如何配置监控表MonTables来实现ASE的监控功能

MDA中的代理表monProcessSQLText包含当前所有会话正在执行的SQL语句。如果已经配置了MDA，可以通过查询该代理表monProcessSQLText来获得正在执行的SQL语句。

在没有配置MDA监控的环境中，可以使用更加通用的命令来查询当前会话正在执行的SQL语句。dbcc sqltext命令需要sybase_ts_role角色才能执行，过程sp_showplan需要sa_role角色才能执行。

下面提供一个存储过程来查询当前Sybase服务器内正在执行的所有SQL语句。思路是：获得当前使用锁的会话ID(spid)，利用游标遍历得到每个spid的正在执行的SQL语句。

use sybsystemprocs
go

if exists (select 1 from sysobjects where (sysstat & 7) = 4 and name = 'sp_currentsql')
begin
  drop procedure sp_currentsql
end
go

print "Installing sp_currentsql"
go
--参数：dbid 允许为空，表示查询相应数据库内的SQL语句！
create procedure sp_currentsql @dbid int = NULL
as
declare @retvalue int,@spid int,@spidcount int
begin
  /*
  ** Must have sa_role to run these commands
  */
  if (proc_role("sa_role") < 1 or proc_role("sybase_ts_role") < 1)
    begin
      print "Must have sa_role to execute sp_showplan and sybase_ts_role role to run dbcc sqltext"
      return(1)
    end

  if @@trancount = 0
  begin
    set chained off
  end
  set transaction isolation level 1
  --set flushmessage on
  set nocount on
  create table #tblspid(spid int)

  if(@dbid is null)
    begin
      insert into #tblspid
      select distinct spid from master.dbo.syslocks where spid > 0
      union
      select distinct spid from master.dbo.syslogshold where spid > 0
    end
  else
    begin
      insert into #tblspid
      select distinct spid from master.dbo.syslocks where spid > 0 and dbid=@dbid
      union
      select distinct spid from master.dbo.syslogshold where spid > 0 and dbid=@dbid
    end

  delete #tblspid from #tblspid a,master..sysprocesses b where a.spid=b.spid and (b.hostname is null or b.suid=0)

  select @spidcount=count(*) from #tblspid where spid<>@@spid
  if(@spidcount>0)
  begin
    declare cur_spid cursor for select spid from #tblspid where spid<>@@spid
    open cur_spid
    fetch cur_spid into @spid
    dbcc traceon(3604)
    while @@sqlstatus=0
    begin
      print "============================%1!===================================================",@spid
      dbcc sqltext(@spid)
      print "-----------------------------------------------------------------------------------"
      --exec sp_showplan @spid,null,null,null
      fetch cur_spid into @spid
    end
    dbcc traceoff(3604)
    close cur_spid
    deallocate cursor cur_spid
  end
  drop table #tblspid
end
go

exec sp_procxmode 'sp_currentsql', 'anymode'
go
grant execute on sp_currentsql to public
go

下载该存储过程：sp_currentsql.sql

相关文章

• 2013-09-08 -- 查看ASE v15正在执行的SQL语句内容 (0)
• 2010-09-10 -- Row-Level Locking for System Tables (0)
• 2010-04-24 -- 如何配置监控表MonTables来实现ASE的监控功能 (0)

Versions of Adaptive Server earlier than 15.0.2 used exclusive table locks on system tables while executing data definition language (DDL) and utility commands. The set of system tables Adaptive Server locked depended on the type of DDL operation you executed. If another DDL running concurrently tried to take a conflicting exclusive table lock on the same system table, this DDL had to wait to acquire the lock on any system catalogs. These DDL operations were executed serially.

This methodology impeded performance in temporary databases, where their DDL activity is very high also, and consequently their catalog contention is very high. This limited the Adaptive Server throughput for applications using temporary tables.
Adaptive Server version 15.0.2 uses row-level locking to resolve these issues:

*

System-table contention, caused a bottleneck for many DDLs and utilities.
*

tempdb contention. Because the system tables are locked at the row level, Adaptive Server 15.0.2 eliminates tempdb contention.
*

Shared or exclusive table-level locks while executing DDLs and utilities. Earlier versions converted most system tables to data-only locking (DOL), but still created shared or exclusive table-level locks while executing DDLs and utilities. Using row-level locks for system tables eliminates this contention.

Adaptive Server sets intent locks on catalogs only, which removes potential contention (An intent lock indicates that page-level or row-level locks are currently held on a table.).
*

DDLs and utilities blocking each other. Adaptive Server 15.0.2 allows DDLs and utilities to run in parallel.

Earlier versions of Adaptive Server used table locks to achieve system catalog synchronization. Adaptive Server 15.0.2 uses intent locks for table-level synchronization and row locks for row-level synchronization. Earlier releases of Adaptive Server locked the entire system catalog while performing operations on the object, so a single lock request was made. However, Adaptive Server version 15.0.2 requests locks for all applicable rows while performing operations on the object if there are multiple rows corresponding to an object in a system catalog.

This change means that Adaptive Server 15.0.2 requests more locks to perform the same operation than earlier releases, and increases the number of lock resources the system needs. Consequently, you may need to change the number of locks configuration option after you upgrade Adaptive Server.

相关文章

• 2019-04-12 -- Sybase ASE及SQL Anywhere数据库修复专家 (0)
• 2015-01-16 -- master数据库配置区域(configuration area)损坏的一种修复方法 (1)
• 2014-10-10 -- ASE对象名称长度限制 (0)
• 2014-06-09 -- 统计用户数据库内所有表的行数 (0)
• 2013-11-19 -- 以HTML格式显示ASE查询计划 (0)
• 2013-11-11 -- Sybase ASE 15.0.3 for windows平台安装文档 – 5、安装后的配置工作 (1)
• 2013-11-11 -- Sybase ASE 15.0.3 for windows平台安装文档 – 4、安装Sybase数据库服务 (0)
• 2013-11-11 -- Sybase ASE 15.0.3 for windows平台安装文档 – 3、升级到 Sybase 15.0.3 ESD #3 (0)
• 2013-11-11 -- Sybase ASE 15.0.3 for windows平台安装文档 – 2、安装Sybase ASE程序 (0)
• 2013-11-11 -- Sybase ASE 15.0.3 for windows平台安装文档 – 1、安装前的准备工作 (1)