September 21, 2010 at 10:36 am
Hi,
I am trying to migrate an application running on WebSphere that uses OptA drivers to connect to SQL Server 2000. The new environment is going to have the same WebSphere but I have been asked to use MS JDBC drivers (instead of OptA) and simultaneously also start using SQL Server 2008.
I tried running the SQL Upgrade Advisor on the 2000 database and that showed no problem with any of the SQL code or the DB.
So I transferred the data in the db to a new db on a Server 2008 machine and made the web server use the MS JDBC drivers.
From as far as I can see, the website (or the web app on WebSphere) seems to be running fine but there is some marked slowness that can be observed. Further more, after running for a few hours (like 6-8 hours) the requests are serviced very slowly. So slowly that the performance tests time out at this point.
1) What are the possible issues that can arise when one migrates from using OptA drivers to MS JDBC drivers?
2) I am completely new to DBA, so I'd appreciate some tips in where to start looking to figure out what the problem is?
Thanks in advance.
September 23, 2010 at 2:13 am
how you have migrate your 2000 server to 2008
have ran the update statistic after your upgrade.
Regards,
Subbu
http://mssqlforum.wordpress.com
Regards,
Subbu
Click here to Get Speedy answer or solution
September 24, 2010 at 4:42 am
Hi Subbu,
I first ran the MS SQL Server Upgrade Advisor to see if any of the SQL I have in my code base would have deprecated code and such things and the Advisor showed no such issues.
Then I replicated the DB, set the compatibility level to 80 for SQL Server 2008 and made it use the new DB. The web app is working but the app runs slower than while it was in the SQL Server 2000. I am trying to investigate why that is so.
Any help/tips on what can be the possible issues is appreciated. Thanks.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply