January 23, 2009 at 9:25 am
DBADave (1/23/2009)
You got it. It's also designed for UNIX/ORACLE. Not sure about SYBASE.
In my experience almost all applications like this experience performance problems. It's probably got problems on the Oracle side too.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
January 23, 2009 at 9:31 am
Same here.
January 23, 2009 at 12:58 pm
Grant Fritchey (1/23/2009)
I haven't run averages on my systems recently, but 20ms just for recompiles seems a bit high for an average.
The 20 is compiles/sec, not sec/compile. There's no counter that I know of that indicates the time taken to compile (though statistics time does)
With a lot of ad-hoc SQL, 20 compiles per sec is much lower than I would have expected. Not saying it's good, but I have seen it much higher on an ad-hos SQL system
Dave: My reason for asking if it was OLTP wasn't about the database design. In general, OLTP sees lots and lots of small, fast queries that return small amounts of data, often with very similar signatures. OLAP sees fewer more complex queries that take longer, return far more data and are typically far more dissimilar.
Which describes your system better?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 23, 2009 at 1:39 pm
The vendor indicated it's a mix of batch and short transactions. We haven't had a good opportunity to witness what occurs more, short transactions or large batch. At night there is a large amount of batch, just from the vendor's product. Our development area has created their own data feeds from our trading systems, billing systems and other business related systems into this product (which is essentially an accounting system). We just found out yesterday the developers have about 60 SSIS packages that run at night. Not a huge number, but they don't have a good grasp of SSIS yet so to find out after the fact is not good news for the DBA team. What that also means is we don't know yet the processing nature of these packages.
During the day there are numerous reports that will run, but the application itself does a lot of quick transacions sheduled to run every minute, every 5 minutes, etc., checking for data to process. So what we believe this means is at night there are a lot of long transactions and during the day there are more short transactions, but that all depends upon the nature of the reports a user decides to run. (ex: give me all activity for the day vs. give me all activity for the week, month, YTD.).
Wish I had a better indication, but at this time I don't.
Viewing 4 posts - 31 through 34 (of 34 total)
You must be logged in to reply to this topic. Login to reply