By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,363 Members | 1,719 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,363 IT Pros & Developers. It's quick & easy.

Production Database Setting DB2 UDB

P: n/a
Hi All,

I am using DB2 UDB enterprise server unlimited edition on linux
platform. We have completed entire database as well as front end (web
application in JSP using JBOSS) development. Its all working fine. We
will be deploying this in production server very soon. But as this is
my first project with respect to DB2 UDB i am little bit concern about
different database level, instance level and system level setting on
database server. Here if any body is knowing which parameter and which
settings need to be considered please let me know because i am in
urgent need of this. I tried to read different book but i didnt got
anything specific. I want ti go for setting with respecty to concurrent
user, heavy traffic on database server , different heap sizes etc.
Thanks
Suresh

Dec 29 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a

Suresh wrote:
Hi All,

I am using DB2 UDB enterprise server unlimited edition on linux
platform. We have completed entire database as well as front end (web
application in JSP using JBOSS) development. Its all working fine. We
will be deploying this in production server very soon. But as this is
my first project with respect to DB2 UDB i am little bit concern about
different database level, instance level and system level setting on
database server. Here if any body is knowing which parameter and which
settings need to be considered please let me know because i am in
urgent need of this. I tried to read different book but i didnt got
anything specific. I want ti go for setting with respecty to concurrent
user, heavy traffic on database server , different heap sizes etc.
Unfortunate it all depends. From what I understand you have not
performance tested your application before going into production? If
so, my best advice is to setup such a test. Try figuring out which work
flows are most critical, and stress test those. From there you should
be able to detect bottlenecks in both DB2 (different settings, bad sql,
missing index, etc) and JBoss (different settings, inefficient code,
etc). You might find the following article interesting. It is a bit
old, but I think it is still relevant:

http://www.db2mag.com/db_area/archiv...q1/hayes.shtml

HTH
/Lennart

Dec 29 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.