Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I suspect there should be no problem as those are separate pieces of software, but ideally I would like to have some ‘official’ confirmation or denial as it will be production environment.
I’m targeting newest versions of both databases.
I was not able to find any information in official channels, but maybe I was looking in the wrong places.
Information about individual successes of failures would also be useful.
The two products can co-exist peacefully because:
There is no overlap in the default installation path for the 2 products;
They don’t require the same TCP port number for servicing requests – DB2 listens on port 50000 while SQL Server listens on port 1433.
Your real worries should be about server load during production.
Without knowing what your current usage is, the installation of another database server will at least impact resource contention and utilization (of CPU, memory, HDD etc).