Comments
Sort by recent activity
I am also getting similar kind of issue, have you got a solution to the problem ?I need it badly. / comments
I am also getting similar kind of issue, have you got a solution to the problem ?I need it badly.
It seems the issue stems from the global lock conflict on flyway_schema_history during the flyway clean process. Try excluding this table or review locking configurations.
/ comments
It seems the issue stems from the global lock conflict on flyway_schema_history during the flyway clean process. Try excluding this table or review locking configurations.
Thanks@fakhru this definitely helped me alot. / comments
Thanks@fakhru this definitely helped me alot.
Same happend with me @aliajmal , lol these kind of silly issues truly just waste your time. / comments
Same happend with me @aliajmal , lol these kind of silly issues truly just waste your time.
David_Keaveny said:
This looks very helpful, especially for non-Windows based build systems. When I try to run the CLI based on the scripts, it fails to connect my local SQL Server - do we need to set up networking to allow the CLI access? There's no indication of it in the examples. My script is:
<div>docker run --rm --interactive --tty \
--mount type=bind,source=/src/scripts,target=/src \
redgate/sqlcompare \
/IAgreeToTheEULA \
/Scripts1:/src \
/Server2:localhost /Database2:MyDatabase /UserName2:Deployments /Password:my-secret-password
</div>
which results in the error message: SQL Compare V14.7.2.20940
====================================================================================================================================================================
Copyright © Red Gate Software Ltd 1999-2022
Beta (expires on Wednesday, 06 July 2022)
Warning: Some settings are missing from the RedGateDatabaseInfo.xml file in the scripts folder '/src': default values will be used for any omitted setting.
Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify<br>that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server: Could not open a connection to SQL Server)
wow, it looks rpomising,I am gonna give it a try and update you guys here . Thanks. / comments
David_Keaveny said:
This looks very helpful, especially for non-Windows based build systems. When I try to run the CLI based on the scripts, it fails to connect my local SQL Server - do we ne...