Activity for Manoj Kumar Jain
-
Manoj Kumar Jain posted a comment on discussion ART Help
db_owner-Rights should solve the issue. I will test and update here for benefit of others.
-
I shifted to developer edition but had same issue but I was not using sa-user. Using sa user solved the issue. Thank you. The question here is ... is it mandatory to use sa user? what permission does a user require? .
-
No specific reason. Just used as it could be used in production environment too. So thought it could be good for testing too. I will try with developer edition and update. Which version of sql server is tested perfectly? I can try that .... Thanks
-
SQL version 2019 express java 8.0.3410.10 tomcat 9.0.65 I tried with default sql jdbc 7.4 as well as with 11.2.0 version downloaded from Microsoft website I hope this helps
-
No, I tried several times by deleting the DATABASECHANGELOGLOCK table. This link has some info https://github.com/liquibase/liquibase/issues/1816 and https://forum.liquibase.org/t/databasechangeloglock-is-created-twice-on-case-sensitive-ms-sql-database/872/4 Some online resources pointed that liquibase version may be an issue so revert to older version. I could not figure out how to revert to older version of liquibase. I have tried with a fresh database created , I will still try again but seems...
-
I am referring to ART Database setting after first start. I am was able to use using default option and test .. it worked as expected
-
When selecting MSSQL as database I am getting following error: An error occurred liquibase.exception.LockException: liquibase.exception.DatabaseException: There is already an object named 'DATABASECHANGELOGLOCK' in the database. [Failed SQL: (2714) CREATE TABLE DATABASECHANGELOGLOCK (ID int NOT NULL, LOCKED bit NOT NULL, LOCKGRANTED datetime2(3), LOCKEDBY nvarchar(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID))] I downloaded new driver version 11.2.0 from microsoft website also but same...
1