Re: Blocking on tempdb*..sysobjects - why is number of open indexes so high ?
> I expect that for some reason the transaction that is inserting into #temp is running in ISO 3 - perhaps to > make sure the select portion is consistent. I would check to see if that is...
View ArticleRe: pool is configured too small for current demands
Dear Varghese, It's obvious that no free space left in data segment, as I recommended before, you have to add space by using "ALTER DATABASE .. " Regarding how to prevent default segment from being...
View ArticleRe: Blocking on tempdb*..sysobjects - why is number of open indexes so high ?
If the app server is using the wrong driver (as is often the case with ASE - people mistakenly assume the jTDS driver shipped with many app servers is ASE compliant - it isn't), that could be an issue....
View ArticleRe: Blocking on tempdb*..sysobjects - why is number of open indexes so high ?
Thanks I should have been more explicit in saying we're using ADO .net and not JDBC.We're on old ADO drivers (ie those without the working set of BCP api's) so have to upgrade.Are the saying the ADO...
View ArticleRe: Blocking on tempdb*..sysobjects - why is number of open indexes so high ?
My bad....you can only see it via dbcc pss(suid,spid) - look for pisolation=# ....should be about line 196 in the output....to see the output, you will need to do dbcc traceon(3604) first..... For...
View ArticleRe: Blocking on tempdb*..sysobjects - why is number of open indexes so high ?
Thanks - I couldn't see anything to reset the connection - but if you find out I also raised the query here C# ADO net driver : Connection Pool not resetting a connection
View ArticleRe: Blocking on tempdb*..sysobjects - why is number of open indexes so high ?
Apparently, it isn't part of the ADO.NET spec....so we don't have anything. Comment from primary support engineer was that a proc such as sp_reset_connection also would be source of...
View ArticleRe: Blocking on tempdb*..sysobjects - why is number of open indexes so high ?
It may not be part of the explicit spec but surely the default action of a connection in the connection pool is that when its returned to the pool for re-use its available in the "correct" state. In...
View ArticleRe: Blocking on tempdb*..sysobjects - why is number of open indexes so high ?
While I partially agree with what you are saying, the rest of it is starting to get argumentative and this is not the forum for such. I can only comment that I see both sides - and just encourage you...
View ArticleRe: Blocking on tempdb*..sysobjects - why is number of open indexes so high ?
Didn't mean for it to be getting argumentative. I'll pass the request through the departments here. Thanks
View ArticleSpeeding up full backup of Replicate database ASE 15.5
Greetings all I need to speed up replicate database backup. ASE version 15.5Adaptive Server Enterprise/15.5/EBF 20633 SMP ESD#5.2/P/RS6000/AIX 5.3/asear155/2602/64-bit/FBO/Sun Dec 9 11:59:29...
View ArticleRe: Speeding up full backup of Replicate database ASE 15.5
Are you performing compressed dumps? What compression level are you using? Compressed dumps can require a good bit more cpu than uncompressed dumps (the amount of cpu resources depends on the...
View ArticleRe: Speeding up full backup of Replicate database ASE 15.5
Mark Thanks for the inputs. We use compression level 2 on both primary and replicate.This was tried out before upgrade to 15.5 and seems good enough. BTW on a different server I also tried new...
View ArticleRe: Speeding up full backup of Replicate database ASE 15.5
The backupserver, and more importantly the sybmultbuf processes that are spawned to do the actual dump/load/compression work, run as separate OS processes outside of the ASE dataserver ... so you need...
View ArticleRe: Speeding up full backup of Replicate database ASE 15.5
I was about to say that I would be looking at the IO subsystem since it is probably phase 1 (direct read from devices) that are slow....and specifically, since filesystems are on SAN - check to see if...
View ArticleRe: Speeding up full backup of Replicate database ASE 15.5
Thanks Mark for the clarifications. The way you explained most of the action seems to be outside ASE dataserver and at OS level. In MDA tables there is only one wait event 85 related to backup...
View ArticleRe: Speeding up full backup of Replicate database ASE 15.5
Thank Jeff. I will certainly ask about synchronous disk replication to SAN team. Though both primary and replicate servers use SAN,the device sizes are different as I noted above. Data and log are on...
View ArticleRe: Speeding up full backup of Replicate database ASE 15.5
Device size - not really. There may be a slight hit when going above 256GB, you are not in that range. The types of devices *could* make a difference - for example, if the replicate server was on...
View ArticleRe: Question about strange cursor behavior - Sybase ASE 12.5.4
Thanks for your replies. I've already solved my problem, just creating a unique clustered index. But I haven't understood what happened yet in the 2 cases above. As suggested by Mark, I've read Chapter...
View ArticleRe: Speeding up full backup of Replicate database ASE 15.5
Hi Avinash.I had the same case in one company.We had 2 database:-on a big device(96 gb)-on a normall device (32gb)The OS Sun- Raw device,DSYNC=FALSE,DIRECTIO=FALSE And when we change device size on...
View Article