Clik here to view.
Re: What's the difference bretween sp_rename and extended alter?
I am using DBArtisan. See screenshot above.
View ArticleRe: What's the difference bretween sp_rename and extended alter?
'extended alter' is not an ASE term so I'd suggest checking the DBArtisan help document (or google search?) to see what 'extended alter' does. In the meantime I'd just use sp_rename and be done with...
View ArticleRe: What's the difference bretween sp_rename and extended alter?
Thank you very much. Will try.
View ArticleRe: statistics and density
thanks for the clarification simon. so if one table in a join does not have a histogram and the other table does, then the available histogram is used for both tables? even then why total density and...
View ArticleRe: statistics and density
If there is a histogram available for only one side of a join clause then the total density of the column will be used. There is no other option. The total density is in essence a consolidation of a...
View ArticleEffective Logging in ASE
How do other people do logging in large systems on ASE ? There are a couple of mechanisms that are commonly used and another less common 1) print messages eg print "%1! %2! Rows affects...
View ArticleRe: Effective Logging in ASE
I would expect some level of contention/performance hit for syb_sendmsg ... - the dataserver has to make a remote call (small performance hit); probably not something you'll want to do in a high-volume...
View ArticleRe: Effective Logging in ASE
> - the dataserver has to make a remote call (small performance hit); probably not something you'll want to do in a high-volume logging situationTrue but the performance hit of sending a record over...
View ArticleRe: Effective Logging in ASE
Table logging is transactional, so it won't work as expected when a ROLLBACK is performed. IMO this is therefore not an option. A non-transactional variation is possible though by using a proxy table...
View ArticleRe: Effective Logging in ASE
It is possible to do non-transactional table logging using a traditional (non-CIS) RPC call to a loopback server entry.
View ArticleRe: Effective Logging in ASE
> Table logging is transactional, so it won't work as expected when a ROLLBACK is performed. IMO this is therefore not an option.Agreed. We only use this for logging successes. We handle errors in...
View ArticleRe: Effective Logging in ASE
True, that should also be in the list. The overhead is probably sizeable though.
View ArticleRe: Effective Logging in ASE
You can also read such a proxy-table-file though the proxy tab itself. And yes, I've seen this used in practice.
View ArticleDDL in Tran Option - Still a bad idea?
I have had quite a few request from developers recently about enabling the option - 'ddl in tran',true I know in the past this was discourage but in recent times Sybase has made most system tables...
View ArticleRe: DDL in Tran Option - Still a bad idea?
Since the row-locked catalogs in 15.0.2, most of those downsides have gone. The same warnings apply as for transactions in general: don't keep them open for too long. Heeding that, there is no reason...
View ArticleRe: SAP ASE 16.0.0.3 - Documentation
Avinash, I have the documentation sets already. Thank you....
View ArticleStack Trace when running update stats - ASE 15.7 SP 100
We migrated our current server from 15.0.3 to 15.7 SP 100 recently. We got the following stack trace when we are running update statistics on a large table ... 00:0013:00000:00525:2014/11/23...
View ArticleRe: DDL in Tran Option - Still a bad idea?
As with everything - it all depends. SAP applications run with ddl_in_tran on all the time without any major issues. It even saved a few days of work when an errant transaction started to drop and...
View ArticleRe: Stack Trace when running update stats - ASE 15.7 SP 100
Probably a knee jerk response (removing tempdb cache) that depending on how heavily your app uses tempdb will cause your app to run slower - if for no other reason, due to cache contention. Most...
View Article