Db2

Our Developers Group is experiencing a problem with executing Queries against DB2 Community Edition (Installed on their Laptops) using Data Studio.  The Queries themselves are executing quickly, however, it looks like there is an issue with it taking forever to reconnect to DB2 every time the Execute SQL trigger is clicked on. (so1.2miliseconds to execute the SQL and 20 seconds to connect to DB2).

First off, I realize Data Studio is sunsetting, so please, no comments on about not using Data Studio (This is already being looked at).  Also, please note that this is Windows, not AIX or Unix.  (And yes, I do feel that there is a reason the "W" is LAST in L...U...W).

Recently, changes were made to use a Service account that is on our DM server.  Although I have suspicions that this is what the "Cause" is, I am hoping someone else has experienced this and knows of a parameter change, either in DB2 or in Data Studio to fix it.

I was thinking this was an issue with the JDBC connection, but I am being told they use Eclipse for their development, and there is a connection to the database using JDBC in there, and it is having no issues.

Before I just give up, I am hoping someone else has had to deal with this.

Thanks,

Side-question.
I've recently jumped back into Db2 after being retired for a while. 
I don't see an end of life date for Data Studio 4.1.4. Is there a doc somewhere that states an end of life date?

Our Developers Group is experiencing a problem with executing Queries against DB2 Community Edition (Installed on their Laptops) using Data Studio.  The Queries themselves are executing quickly, however, it looks like there is an issue with it taking forever to reconnect to DB2 every time the Execute SQL trigger is clicked on. (so1.2miliseconds to execute the SQL and 20 seconds to connect to DB2).

First off, I realize Data Studio is sunsetting, so please, no comments on about not using Data Studio (This is already being looked at).  Also, please note that this is Windows, not AIX or Unix.  (And yes, I do feel that there is a reason the "W" is LAST in L...U...W).

Recently, changes were made to use a Service account that is on our DM server.  Although I have suspicions that this is what the "Cause" is, I am hoping someone else has experienced this and knows of a parameter change, either in DB2 or in Data Studio to fix it.

I was thinking this was an issue with the JDBC connection, but I am being told they use Eclipse for their development, and there is a connection to the database using JDBC in there, and it is having no issues.

Before I just give up, I am hoping someone else has had to deal with this.

Thanks,

Our Developers Group is experiencing a problem with executing Queries against DB2 Community Edition (Installed on their Laptops) using Data Studio.  The Queries themselves are executing quickly, however, it looks like there is an issue with it taking forever to reconnect to DB2 every time the Execute SQL trigger is clicked on. (so1.2miliseconds to execute the SQL and 20 seconds to connect to DB2).

First off, I realize Data Studio is sunsetting, so please, no comments on about not using Data Studio (This is already being looked at).  Also, please note that this is Windows, not AIX or Unix.  (And yes, I do feel that there is a reason the "W" is LAST in L...U...W).

Recently, changes were made to use a Service account that is on our DM server.  Although I have suspicions that this is what the "Cause" is, I am hoping someone else has experienced this and knows of a parameter change, either in DB2 or in Data Studio to fix it.

I was thinking this was an issue with the JDBC connection, but I am being told they use Eclipse for their development, and there is a connection to the database using JDBC in there, and it is having no issues.

Before I just give up, I am hoping someone else has had to deal with this.

Thanks,

Edward, 

One reason is that the database might not be active.  On first connect, Db2 will allocate log files and memory. This can make the first connection take a bit of time. 
If you have Db2 command window, try : db2 activate db <dbname> 

Then run your query. 
Regards,

Bill 

Our Developers Group is experiencing a problem with executing Queries against DB2 Community Edition (Installed on their Laptops) using Data Studio.  The Queries themselves are executing quickly, however, it looks like there is an issue with it taking forever to reconnect to DB2 every time the Execute SQL trigger is clicked on. (so1.2miliseconds to execute the SQL and 20 seconds to connect to DB2).

First off, I realize Data Studio is sunsetting, so please, no comments on about not using Data Studio (This is already being looked at).  Also, please note that this is Windows, not AIX or Unix.  (And yes, I do feel that there is a reason the "W" is LAST in L...U...W).

Recently, changes were made to use a Service account that is on our DM server.  Although I have suspicions that this is what the "Cause" is, I am hoping someone else has experienced this and knows of a parameter change, either in DB2 or in Data Studio to fix it.

I was thinking this was an issue with the JDBC connection, but I am being told they use Eclipse for their development, and there is a connection to the database using JDBC in there, and it is having no issues.

Before I just give up, I am hoping someone else has had to deal with this.

Thanks,