[Bitbucket] Problem using Databasemigration-wizard with SQL Server

[Florian Bodenheimer]

Hi,

we had Bitbucket running on a Mysql-Database for test-purpose and want to move it to a new server and a sql-server-database now. Unfortunately the migration-wizard isnt able to connect to the new database. I guess this is related to the sql-server-named-instance issue with the new driver.

If both a portNumber and instanceName are used, the portNumber will take precedence and the instanceName will be ignored.

https://confluence.atlassian.com/jirakb/updating-jdbc-url-for-microsoft-sql-server-934718842.html/

Port is a mandatory field. I am not able to leave it empty. Does anyone have a solution for this problem?

Thanks,

Best regards,

Florian

[Florian Bodenheimer · Accepted solution]

Hi,
I solved the problem using SQL-Express-Server without named instance.

1. Installed SQL-Express without named instance on a Testserver
2. Migrated the Bitbucket-Database from Mysql to the SQL-Express-Server
3. Exported database manually from SQL-Express-Server to the named instance
4. Configured migrated database in named instance in bitbucket.properties

Best regards,
Florian

[Christian Glockner]

Hi Florian,

Is there any reason you can't just specify the hostname and port number of your SQL Server instance? If TCP/IP is enabled (which it needs to be anyway), then you should be able to use just that.

Cheers,

Christian

Premier Support Engineer

Atlassian

[Florian Bodenheimer]

Hi Christian,

and thanks for the reply. The problem is that the driver seems to ignore the instancename when a port is specified.  But port is a mandatory field.

Best regards,