1> admin who, echo "Hello", with_log
2> go

I. 2006/11/25 13:49:13. User 'sa' writes: 'Hello'

1. Create a connection to a non-existing database, for example, 'XXX.XXX'. In the create connection command, specify a login name that (i) marks the unique placeholder string you're trying to write to the RS errorlog, and (ii) is guaranteed not to exist if 'XXX' would happen to be an existing dataserver, e.g.:

   create connection to XXX.XXX
   set error class to rs_sqlserver_error_class 
   set function string class to rs_sqlserver_function_class
   set username to ___my_unique_string___
   set password to doesntmatter
   with dsi_suspended
   

2. When you want to write your placeholder string to the RS errorlog, run these commands:

   resume connection to XXX.XXX
   go
   suspend connection to XXX.XXX
   go
   

Although the login into XXX.XXX will fail (that's the idea!), the name of the login -i.e. your placeholder string- is written to the RS errorlog as a result:

I. 2006/11/25 13:53:11. Trying to connect to server 'XXX' 
as user '___my_unique_string___' ......

3. Note that it is not a good idea to use the dataserver name of database name as your placeholder string. When starting RepServer, the name of the connection will be written to the RS errorlog as part of a warning that teh connection is down.

-- define the tables
create table t1 ( a int, b int)
create table t2 ( c int, d int)
create table t3 ( e int, f int)
go

-- this query works fine
select *
from t1 
inner join t2 on t1.a = t2.c
inner join t3 on t2.d = t3.f

select *
from t1, t2, t3
where t1.a = t2.c 
  and t2.d = t3.f

-- this query runs into syntax error 11040
select *
from t1 
inner join t3 on t1.a = t2.c
inner join t2 on t2.d = t3.f
go

Msg 11040, Level 16, State 1
Server 'PROD', Line 3
Adaptive Server cannot perform the requested action 
because column 'c' is not within the scope of the 
joined table expression. Check your command for 
missing or incorrect database objects, variable 
names, and/or input data.

• create a proxy table, mapping to the real table
• use a dedicated login for the proxy table's CIS access (i.e. create an external login)
• set up a login trigger for that login, which contains a waitfor delay statement
• when querying the proxy table, the waitfor delay in the login trigger kicks in, thus causing a delay in query execution

sp_addserver loopback, null, @@servername
go

-- For some reason, you need to make sure the statement cache 
-- is disabled, or things won't work...
sp_configure 'statement cache', 0
go

use my_db
go
sp_rename my_table, my_table_renamed
go
create proxy_table my_table at 'loopback.my_db..my_table_renamed'
go
grant all on my_table to public
go

use master
go
sp_addlogin loopback_login, mysecretcode, my_db
go
sp_addexternlogin loopback, my_login, loopback_login, mysecretcode
-- check the docs for details about sp_addexternlogin !
go
use my_db
go
sp_adduser loopback_login
go
grant all on my_table_renamed to loopback_login
go

use my_db
go
create proc my_logintrig
as
if suser_name() = 'loopback_login'
waitfor delay '00:00:10' -- perhaps a bit much...
go
grant all on my_logintrig to public
go
sp_modifylogin loopback_login, 'login script' , my_logintrig
go

sp_dropexternlogin loopback, NULL
go

use my_db
go
create proc my_proc 
as 
waitfor delay '00:00:10'
select * from my_table_renamed
go
create existing table my_table2 (...all columns...) 
external procedure at 'loopback.my_db..my_proc'
go
grant all on my_proc to public
go